I saw a message on Friday as below :
"All APis under the hub.docker.com/v1/repositories are going to be shutdown on September 5th 2022"
How can i check if Im affected? I dont seem to find where I can do this?
Related
I've a custom Docker image based on 7.4-Apache that is being used for f1 instance type of compute engine. I successfully deployed and my website is reachable but after around 30 minutes or less the health check times out and then the container crashes.
I tried to see if there are any logs to investigate if this is an application issue or something else.
I wanted to ask are there any logs which I can see what's going on, if not how can I add logs?
Since I don't know your exact configuration I can point you to some documentation at this point.
First have a look at Cloud Audit Logs documentation - it describes how to view logs and find what you need. You will find more here about viewing audit logs.
Try looking for related logs in logs viewer.
Also have a look at how to contruct query to extract information you're looking for.
If you provide more details about you congiguration I might be able to give a more precise answer.
After upgrade to TFS 2018 Update 2 (with Azure DevOps 2019 still persisting), some service hooks messages are not sent correctly but are stuck in the queue with status Queued or Processing (see the image). Messages in Processing state appear to be delivered correctly to the receiver, the ones in Queued state not. Service hooks are working for 1-2 days correctly after a restart, next days are more and more buggy. Receiver side is ok, many times tested.
This happens on all service hooks (some are HTTP webhooks, other posts to Teams), in 2 of our 3 collections. On the 3rd collection, it works without issues. Disable/Enable or recreating the hook doesn't help. Is there any way how to debug service hooks or some log.
Also reported here. Received several patches from MS but with the same result. Installed Azure DevOps 2019 with the same results.
Any help would be appreciated.
The answer is - this is a Microsoft and TFS problem. After several months of communication with Microsoft and trying several patches for this problem, finally, the right patch arrived. And the problem is solved.
The patch is non-public now, so if you are experiencing a similar problem, ask Microsoft support.
Edit: Problem is fixed also in official release 2019.0.1. See Release notes
We recently added "Publish To Apple News" plug-in to our Word Press and getting "Date_Not_Recent" error. After talking to the developers and checking their support pages, it looks like it is a a time zone issue between the WP server (Oregon, US with UTC timezone) and Apple News Publisher (which till this moment Apple can't tell me where it is located, i assume California, but who knows for sure?)
Solution, is to sync those time zones together. My questions:
1- Anyone had any issues rezoning their aws servers?
2- If you had this issue before, what did you do?
I am just trying not fix one thing and break 10 other things in return. just being cautions. We all know that Murphy's law roles in IT.
Thanks in advance
We figured it out. it was an NTP issue.
We host on AWS, and the time sync packages (NTP) were a little bit out of sync, so we deleted them and installed chrony instead and that worked.
For anyone who is interested, here are the instructions (under configuring the Amazon time sync services):
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html
I have read a dozen articles on here, and tried over 50 different syntax variations in task scheduler, and bat files with several different syntax variations, and it still will not work. All of the articles' answers fail, along with everything else I have tried.
Here's the task: Monday through Friday at 4:55 AM, launch a browser and navigate without user interaction to westcoastswing.radio.net. It doesn't matter which browser. Task must run Monday through Friday only. Task must run whether anyone is logged in or not, and must wake the computer to run the task. Monday through Friday at 6:15 AM, kill the browser.
Updating to a newer version of Windows is not an option at this time. A third party product is only an option once it's determined that Microsoft is deliberately blocking this functionality. Using Windows Media Player and a specialized URL found via F12 might be an option, but I have spent an even greater amount of time trying to get that strategy to work, without success.
Thanks for any help or advice. Please don't mark this as a duplicate, I have tried the existing similar articles and their solutions do not work.
Found a method that works, but only because I use MSIE only for this and nothing else.
Specify full path to IE, in quotes, in start program.
Specify URL, not in quotes, in optional arguments.
Highest possible permission.
Don't run "hidden".
I don't know why that worked, or why out of all the combinations I tried before I didn't hit on that exact one, but sorry for posting a pointless question.
We have a few backend windows services written in .net framework 1.1 running and on December 31st 2008 around 5.00 pm (EST) we stopped these services to run some year end reports.After the reports were run , we tried to start the services and the moment we attempt , it would give an error "Service did not start in a timely fashion".We tried every possible things that google came up with.Service Packs , WinDbg , GFlags etc etc.
Finally we called in Microsoft support around 10.30pm(we had premium support contract with Microsoft) and they started collecting all kinds of server data and around 12.05 am (EST) the services starting successfully with no issues.We hadn't done anything different or special to get it started.The whole team was stumped as to what was happening and equally glad that it was working.
The conclusion is Microsoft support team thinks that this could very well be something to do with the .NET Framework 1.1 namepsace System.ServiceProcess.ServiceBase inability to support leap year.They havent confirmed it yet and are still investigating.
I will keep posted as and when I have updates form MSFT support.I was planning for a dreadful 2009 start but gladly it all ended fine.
I wonder if the bug is related to the one that causes Zune 30GBs to lock up on 31 December in leap years: it tests for day>365 in one place and day>366 in another and as a result when day=366 it falls through the second test and goes in to an infinite loop.