Clock time issue in c3560 Logs:

Hi my name Izhar,
I am facing the issue with C3560 switch.
i have set the clock which is showing correctly but in Logging it's getting the incorrect time.
please any one help.
acc-ingles-up-00#sh clock
10:08:36.366 UTC Thu Jul 5 2012
below the logs :
1y8w: %LINK-3-UPDOWN: Interface FastEthernet0/12, changed state to down
1y8w: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down
1y8w: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up
1y8w: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down

I had tried the command but after that the issue was not resolved.I have used the below command to fix it:switch(config)#service timestamps log datetime
The command I recommend you use last "serv time l d s l" is the "shortcut" of this command you're using.
Thanks for the ratings.

Similar Messages

Login Window clock shows incorrect time, clock time fixes itself after log in...

Good Evening,
This morning I turned on my MacBook Pro and while I was typing my password to log in, I noticed that the time in the login window clock had a wrong setting. The time displayed was 4 hours delayed in relation to my time zone. However, after logging into my user account I looked and the menu bar and when the clock got displayed, the correct time of my time zone appeared.
I don't know what could have caused this issue. The only thing I know is that yesterday evening, I was using my MacBook Pro with Windows 7 via Bootcamp and used it for a prolonged time (about 5 hours), and then shutdown the computer and did not touch the computer until this morning. Could these issues be related? I know OS X and Windows measure their times differently because the former OS calculates time in relation to UTC and the latter OS calculates the time using the actual zone you have specified in the time settings.
Other than that the issue has not manifested itself again since this morning but I haven't booted into Windows just yet.
Thanks for your time!

Make sure the time and date are correct.
Open System Preferences > Date & Time then select the Date & Time tab.
Select: Set date and time automatically
Then select the Time Zone tab.
Select: Set time zone automatically using current location
If that doesn't help, open the Finder. From the Finder menu bar click Go > Go to Folder
Type or copy paste the following:
~/Library/Preferences/com.apple.systemuiserver.plist
Click Go then move the coml.apple.systemuiserver.plist file to the Trash.
Then restart your Mac and check the time ...

Logging Time issue with Job running under SYS.MAINTENANCE_WINDOW_GROUP

Hi,
We have configured a nightly job to run daily at 2:00 AM
And configured the Job to run under Sys,maintenance_window_group.
The nightly job is producing some log(trace) files in the format
<date-time> message
the <date-time> entry is made as
UTL_FILE.PUT_LINE (log_file, TO_CHAR(SYSDATE,'DD/MM/YYYY HH24:MI:SS') || ' ' || msg, TRUE);
the problem is the entry for date-time field in the log file is not correct.
06/02/2013 20:00:02 NIGHTLY_JOB Begin
It is using EST time ( e.g.- 20:00:00 PM ) but the job is running at timezone Europe/VIENNA
the file modifcation time is OK, when we check it with ls command ( it gives time near to 2:00 AM)
-rw-r--r-- 1 oracle asmadmin 3494 Feb 7 02:36 NIGHTLY_JOB.log
could you please suggest what could be wrong?
Oracle release is 11.2.0.2

hi,
Can you , paste the o/p of
select * from NLS_DATABASE_PARAMETERS;Thanks,
Ajay More
http://www.moreajays.com

Solaris 10's Container server.log time issue

We have tow containers on Solaris 10, and there times zones are ok including Global timezone, but one of the container's server.log file time is incorrect, every log is logging time +1hours. We would appreciate if anyone tell us how to correct time of server.log file. Thank you. KMT

We have tow containers on Solaris 10, and there times zones are ok including Global timezone, but one of the container's server.log file time is incorrect, every log is logging time +1hours. We would appreciate if anyone tell us how to correct time of server.log file. Thank you. KMT

Problem on Oracle11g2 RAC -- PRVF-5424 : Clock time offset check failed

I have a lot of file core wrrote every 6 hour and the same time of alert"node".log file show error about PRVF-5424 : Clock time offset check failed.
Yesterday I use this:
[root@hostname2 ~]# service ntpd stop
[root@hostname2 ~]# ntpdate
[root@hostname2 ~]# service ntpd start
in order to resolve but today the problem re-begin?
2013-04-17 20:23:06.063
CRS-10051:CVU found following errors with Clusterware setup : PRVF-5424 : Clock time offset check failed
PRVF-5413 : Node "" has a time offset of 69695.6 that is beyond permissible limit of 1000.0 from NTP Time Server "******"
PRVF-5413 : Node "" has a time offset of 69940.6 that is beyond permissible limit of 1000.0 from NTP Time Server "**
2013-04-18 02:23:08.973
CRS-10051:CVU found following errors with Clusterware setup : PRVF-5424 : Clock time offset check failed
PRVF-5413 : Node "" has a time offset of -1826.9 that is beyond permissible limit of 1000.0 from NTP Time Server "1***
PRVF-5413 : Node "" has a time offset of -1364.2 that is beyond permissible limit of 1000.0 from NTP Time Server "1**
2013-04-18 08:23:16.093
CRS-10051:CVU found following errors with Clusterware setup : PRVF-5424 : Clock time offset check failed
PRVF-5413 : Node "" has a time offset of -2698.5 that is beyond permissible limit of 1000.0 from NTP Time Server "1***
PRVF-5413 : Node "" has a time offset of -1998.7 that is beyond permissible limit of 1000.0 from NTP Time Server "1***

What is your OS name and version ?
In general you can solve these issues by configuring NTP service running on your cluster nodes to be synchronized with other NTP servers. For example on Linux please read "Oracle RAC and NTP" in http://www.oracle-base.com/articles/linux/linux-ntp-configuration.php#oracle-rac-and-ntp.
Edited by: P. Forstmann on 18 avr. 2013 13:35

Clock/time incorrect after upgrade to bootcamp 5 running windows 8-64

Since I did the upgrade to bootcamp 5 running windows 8-64, (which solved all the previous problems), the clock/time changes by itself to be off by hours frequently throughout the day.

I'd suggest you upgrade to OSB10.4.0.1.0 release.
Webtool taking ages is probably related to some other OS issue, check /var/log/messages and whatever and check your DNS settings are all correct.
What about obtool commands, are they also slow?
Thanks
Rich

How change sStart and End Date and time in the Audit log ???

Install C2S BM39SP1. Work.
Go to the: https://bmserver:8009
Open : VPN Monitor | Audit log information.
Problem - can not cahnge Date and time in the Audit Log Start(End)
How i vcan do this ?
How i can get every day stat log:
login ; date_time_login ; dtae_timie_logout ; bite_in ; bite_out
Serg

Serg,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

[SOLVED] Yet another time issue...

Hi there,
I'm having some crazy, hair pulling, head banging UTC time issues on both my dual boot (Arch & Windows 8) desktop and single boot laptop.
I've been searching and following a mulitude of old threads and the official Wiki guide, however, I simply cannot get UTC time to stay correct between reboots. I've installed Arch a fair few times now, both before and after the switch to systemd and in dual and single boot setups and have never had time related issues like this before...
Here's a run down of the whole sorry story....
Fresh install - set time with hwclock --systohw utc as suggested in the beginners guide.
First boot - time an hour out - huh? cat /etc/adjtime and ls -l /etc/localtime - everything as it should be... UTC and symlink to /usr/share/zoneinfo/Europe/London. Nonetheless I duly follow the Time guide on the wiki, get to know timedatectl a bit, and soon after, time is set to be correct. Great.
Reboot. Time an hour out. Whaaaa??. Start googling, finding a plethora of bbs links to others with similar issues, decide to use NTP. Install, ntpd -qg. All good again. Time right. Phew...
Reboot. Nope. Arrrrgggghhhh. (Bare in mind - at this point I haven't even booted the Windows 8 disc, and I went through the exact same process on my Arch only laptop...)
More googling, thread reading. Find out that hwclock and ntp might be in conflict. Delete /etc/adjtime, reinstall tzdata, re-follow Time article to the letter and reenable NTP to start at boot.
Reboot - time is foward an hour yet again. Bang head repeatedly on desk. Then suddenly - 10 mins or so after boot - NTP kicks in, and time is magically goes back an hour to the correct time! Surely NTP should be doing this early in the boot process, not 10 minutes after? But OK, at least something is happening...
Next I dare to boot into Windows, and yup, time an hour out. Expected, but frustrating nonetheless. Add the registry tweak as suggested in the guide, and turn off the Windows time synchronisation. During which I noticed that Windows 8 time is set to UTC by default, not localtime, which is what the wiki says. Is this a Windows 8 thing?
I can't help thinking, that if this is the case, and the Wiki advise is written under the assumption that Windows time is always localtime, that perhaps this is the route of my problem....
Anyway, Windows time all good now, reboot Arch, time again wrong untill NTP finally kicks in - sigh. Reboot to Windows. Time an hour back. Gaaaahhhh - WTF?!! reset it to be correct. Try again. Same thing. Oops, forgot to mention that on each reboot, I check the BIOS clock, which remains persistently correct during the whole debarkle...
Ok, so I try without the registry hack and turn Windows sync back on. Still fucked. I try various combinations of the two, I try resetting Arch time over and over again. With NTP - late sync. With hwclock only, or both hwclock & NTP - totally fucked! Eventually, I give up on UTC in Arch, set it localtime, delete registry key, turn Windows time sync back on, and thus far all good......
TL;DR - couldn't get hwclock to set UTC time correctly across reboots. NTP worked (sort of), but after each reboot it would take ten minutes for the time to sync and the clock to move back an hour to the correct time. Localtime just works...
My question is - why is the wiki (and the timedatectl status output for that matter) - so adamant that we should use UTC? From what I can gather, as long as I boot Windows around the DST time. or manually move the clock forward or back an hour - all should be well, no? Or are there other issues that I may run into that I've missed? The thing I'm most concerned about is data corruption due to timestamp issues...
Also, why does the wiki repeatedly say that Windows uses localtime, when this doesn't appear to be the case in Eight? Does the wiki need updating or is Windows lying to me? I know which I'd put my money on ;-)
Finally can anyone explain why my time was always an hour forward after a reboot, even when the time was set correctly before, the BIOS showed the correct time, and NTP was in use?
Sorry for the crazy long posting, but this issue has been driving me totally batty!! Any light-shedding greatfully appreciated :-)
Last edited by knowayhack (2013-08-10 15:24:09)

Ok, so I set the clock back an hour in the BIOS, booted Windows - time right - YAY.
Rebooted Arch - time right. OMFG - pure joy!!!
I have to say, I still find it odd that this is how it works, and would like to confirm that things are looking as they should in the output from the following commands....
toby@archy ~ > timedatectl status
Local time: Sat 2013-08-10 15:42:56 BST
Universal time: Sat 2013-08-10 14:42:56 UTC
Timezone: Europe/London (BST, +0100)
NTP enabled: n/a
NTP synchronized: no
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2013-03-31 00:59:59 GMT
Sun 2013-03-31 02:00:00 BST
Next DST change: DST ends (the clock jumps one hour backwards) at
Sun 2013-10-27 01:59:59 BST
Sun 2013-10-27 01:00:00 GMT
toby@archy ~ > sudo hwclock --debug
sudo: timestamp too far in the future: Aug 10 16:39:24 2013
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
[sudo] password for toby:
hwclock from util-linux 2.23.2
Using /dev interface to clock.
Last drift adjustment done at 1376148264 seconds after 1969
Last calibration done at 1376148264 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2013/08/10 14:43:20
Hw clock time : 2013/08/10 14:43:20 = 1376145800 seconds since 1969
Sat 10 Aug 2013 15:43:20 BST -0.953640 seconds
Is it OK to now reinstall NTP to keep the clock in sync on Arch, and are the Windows reg tweaks still necessary on Windows 8?
Thank you guys SOOO much for all the unbelievabley speedy help on this issue - you have no idea how much this has been stressing me out!!
Last edited by knowayhack (2013-08-10 14:54:31)

ESS Timesheet error with Clock Times

Hi everyone,
Has anyone seen this issue? (ERP 6.0, EP 7):
Timesheet data entry profile is configured 'With Clock Times' and WITHOUT 'Release on Saving'. On the daily view of the timesheet, when clock times are entered and Refresh or Review is depressed, the number of hours is populated and the following error displays:
"Number of hours not valid when Start Time and End Time are entered"
This only displays:
- when the profile is configured without 'Release on Saving' checked. When it IS checked, the error goes away.
- from the daily view (no clock times on the Weekly View)
- in the portal timesheet, not via CAT2 in ECC
Any suggestions?
Thanks!
Message was edited by:
Frederic Wood

<u>Without checking 'Release on saving':</u> The system checks the number of hours value with the corresponding hours mentioned in IT0007.
<u>On checking 'Release on saving':</u> It overwrites the number of hours stored in IT0007 in the back end system.
This happens because this option has dependency with 'With Clock times' option. For this option, the system automatically deducts unpaid breaks, as determined in the employees's work schedule, when calculating the number of hours.
If this helps, pl do reward.
Thanks
Narasimha

[SOLVED] System clock / Timezone issues

Hey everyone,
The issue, as it appears to me, is that arch is assuming that my timezone is +00:00, or UTC. I don't really understand why (it should be +10:00) but here is the output to the frequently requested information for this issue
$ cat /etc/adjtime
0.000000 1349592374 0.000000
1349592374
UTC
$ date
Sun Oct 7 07:42:52 UTC 2012
$ date --utc
Sun Oct 7 07:43:18 UTC 2012
$ hwclock --debug
hwclock from util-linux 2.22
Using /dev interface to clock.
Last drift adjustment done at 1349592374 seconds after 1969
Last calibration done at 1349592374 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2012/10/07 07:43:54
Hw clock time : 2012/10/07 07:43:54 = 1349595834 seconds since 1969
Sun 07 Oct 2012 07:43:54 UTC -0.969672 seconds
$ ls -l /etc/localtime
lrwxrwxrwx 1 root root 37 Oct 7 06:39 /etc/localtime -> /usr/share/zoneinfo/Austalia/Brisbane
$ hwclock --show --utc
Sun 07 Oct 2012 07:44:53 UTC -0.687942 seconds
$ hwclock --show --localtime
Sun 07 Oct 2012 07:44:57 UTC -0.281630 seconds
I'm using sytemd, have no rc.conf file, my BIOS clock reported being in UTC. I've been trying to fix this issue for the past few hours (including searching the wiki entries for time, beginner's guide, systemd and many other user's issues related to the clocks/timezones.)
I hope it's just a case of I missed something crucial somehow. Any help is greatly aprpeciated
Last edited by hungryb (2012-10-07 08:40:58)

skunktrader wrote:You didn't need to reinstall tzdata. The reason for your error was a typo in the symlink
lrwxrwxrwx 1 root root 37 Oct 7 06:39 /etc/localtime -> /usr/share/zoneinfo/Austalia/Brisbane
Yeah, that's true, but I'd been remaking symlinks and changing the clock for a while before that iteration, I think it was only that version of the symlink that contained a spelling error.

Every time I try to log in to FaceTime it always says that emails is already use and I don't know why

Every time I try to log in to FaceTime it always says that emails is already use and I don't know why

Hi Joselyntapiapatino,
Welcome to the Support Communities!
The article below may be able to help you with this issue.
Click on the link to see more details and screenshots.
iOS: FaceTime is 'Unable to verify email because it is in use'
http://support.apple.com/kb/TS3510
Cheers,
- Judy

QuickWeb Clock Time

Pavilion G4-1229dx, Windows 7 64 bit
When the Windows clock is set to the correct local time, the QuickWeb time is too hours fast.
To get QuickWeb clock to the same time as the Windows clock, I must set the QuickWeb clock to use a time zone two hours earliert than my local time zone.
This work around does the job but I don't think it should work that way. I've tried changing the Windows internet sync location, tried manually settiing one clock, both clocks, and not manually setting either clock; the Bios time is correct. Nothing helps. I've run out of ideas.
Any suggestions for getting the QuickWeb clock and the Windows clock on the same time zone showing the correct local time?
I looked at some HP laptops on display in stores and they have the same two hour error.
Thanks,
Rich

HP is offering to replace or refund the price paid for the laptop as they are unable to fix the issue nor have any matching replacement....
All those having HP laptops, its a good opportunity to check your Quick web clock time and if it doesnt match Windows clock time (which i am 100% sure will not), then approach HP Support and escalate for replacement / refund....irrespective of how old your machine is this issue is inherent problem in all HP machines for which you should be duly compensated
Dont miss this chance of recovering the value for money paid to HP
Cheers!
Tim

RV220W System Time Issue in Combination with WiFi Active Time

Hi
Have system time issues with rv220w!
Setup:
Note that the real time is 17.32 (bottom right) but the system time is 16.20, result 1h offset (sad that the possibility to configure summertime start/end is missing)
Setting up the WiFi active time from 5.30PM until 6PM (testing only):
Note that the real time is 17.44, the WiFi is "Disabled". The RV220W system time is 16.44 with setting "CET +1h".
BUT:
Even when i change the RV220W system time to a Time/Date offset GMT +2h EET has this no issue to the WiFi time profile i set up. The WiFi stay down.
Note:
The WiFi Active Time Settings only working correct when the Clock Source is setting up with "Set Date and Time Manually" (in "Administration" "Time Settings"), but that is not the way.... i don't like to configure time settings manually (no system administrator will do that tinking)
Conclusion:
I think that the WiFi Time setting does not work fine, mean that the WiFi does not include the configured offset as usually system does....
Further:
RV220W firmware is up to date....
Hope Cisco will fix that and add the summer time feature (like in other systems and other manufacturer) in the next FW.....

GJinAmsterdam wrote:
I have a MacBook upgraded from Tiger 10.4 to *Snow Leopard OS X 10.6.1.* I'm now using *Time Machine* to make back-ups on a *MiniMax external drive* through an USB connection. However, I wish to make wireless back-ups by connecting the external drive to my *Airport Extreme*. I learned that this wasn't possible until the recent release by Apple of the software update "*About Time Machine and AirPort Updates v1.0*".
this has been possible for a long time, since about February 2008 when those updates came out.
The minimum system requirement for this software update is OS X 10.5.2. I should think this requirement is met because I have upgraded to 10.6.1. But when I try to install the software I get the message that the system requirement is at least 10.5.2. and as a result *I can't continue installing*. Apparently my OS update is not recognized by the software. Is there a solution for this problem? Many thanks.
you don't need to install those updates. they are for leopard, not snow leopard. you should be fine as is. do keep in mind that TM backups to air disks are not "officially" supported but they have worked for a long time. also, keep in midn that you'll need to start a new backup sequence once you move the drive to AEBS as remote backups are stored differently from directly attached ones.

Clock freezing issues

I Have reviewed the support article on issues with time and date and have tried all the recommended solutions but I am still having the clock freezing issue on my 5c. I have noticed that when I turn the airplane mode on then off that briefly fixes/updates the time. But the clock doesn't stay correct for long and will later be the wrong time again. i can't figure out if this is a phone issue or a cellular issue. Anyone have any ideas/solutions?

I feel your pain, though I would recommend the 9850 that Verizon does have out. It's a HUGE improvement on the Storm 2. I would switch to it myself but T-Mobile doesn't offer it. So, I'm waiting on BB10 myself.
That being said, you can make a backup of your device before wiping the data. That way you don't lose all your contacts, etc. I would recommend making the backup, wiping the device and seeing how the device responds with no data on it. If it solves the problems then simply add back the databases that you really need from the backup file.
If it doesn't solve the problem then a reload of the OS may be the next step before restoring the backup file.
John
1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you!

OVM 3.0.3 Time Issues

I have a two server pool and after the reboot from installing the 3.0.3-150 patch, the two virtual servers in my pool came back online with drastically different RTC times. Their ntpdate offsets at boot were 23,375 seconds and 21,577 seconds; before this reboot, the largest ntpdate offset had been under 0.002 seconds. Due to NTP, the systems' time on the virtual servers were corrected; however, the RTC remained wrong. This was confirmed by using hwclock after soft linking /dev/rtc to /dev/rtc0.
All my 32bit PVM guests are running kernel 2.6.18-238.1.1.0.1.el5xen and I've been able to fix this issue by configuring xen.independent_wallclock = 1. However, my 64bit PVM guests are running kernel 2.6.32-200.13.1.el6uek and can't be configured with xen.independent_wallclock. The 64bit guests don't get hung when migrating between the servers; however, the time on the 64bit PVM guests still jumps by 30 minutes when I migrate between the servers. NTPD on the guest doesn't update the clock because the offset exceeds the sanity limit of 1000 seconds. I can manually fix the system time by running ntpdate; however this would be something I'd need to check after each migration, which isn't practical. I've ran "hwclock --utc -w" on the virtual servers but they're already about 20 seconds fast after less than a week.
Correct me if I'm wrong, but it's my understanding that the configuration of NTP on the virtual servers is only keeping their system times in check. If NTP isn't keeping the RTC of the virtual servers on time, then how can I ensure that my 64bit PVM guests are getting accurate time from the virtual servers when they live migrate? Or is there a way to make PVM's running kernel 2.6.32 keep time totally independent from the virtual servers?
I didn't have any time issues on guest servers prior to 3.0.3 (this includes running OVM 2.2, 3.0.1, and 3.0.2). Because I never had issues, I never looked closely to how the virtual servers were configured. Did something get changed in version 3.0.3 that would cause these time issues?

user4400470 wrote:
I have a two server pool and after the reboot from installing the 3.0.3-150 patch, the two virtual servers in my pool came back online with drastically different RTC timesWe currently have a fix in QA to fix the symlink (which you've already done, it seems), which will allow the hwclock to be set correctly on boot/reboot.

Clock time issue in c3560 Logs:

Similar Messages

Maybe you are looking for