cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.

2348
Views
15
Helpful
6
Replies
Dulal Ray
Beginner

ACS showing incorrect timestamp in logs.

Hi...We recently installed a patch 5.3.0.40.2 in our ACS server. Post patch installation its showing wrong timestamp. ACS server clock and timezone configuration if correct but still logs showing wrong timestamp. We configurgure timezone Asia/Kalkota( GMT+5.30 ) but in logs timestamp is showing GMT time..

Please help me...

Regards,

Dulal....                  

6 REPLIES 6
ronaldlau2012
Beginner

Hi Dulal,

Im also having this issue with patch 5.3.0.40.7 on a ACS 1121. Time is correctly configured on the server. These are the outputs:

TSJACS-SEDEPP1-01/acsadmin# sh ntp
Primary NTP   : 172.24.254.1

synchronised to NTP server (172.24.254.1) at stratum 4
   time correct to within 69 ms
   polling server every 1024 s

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
127.127.1.0     LOCAL(0)        10 l   61   64  377    0.000    0.000   0.001
*172.24.254.1    172.24.254.3     3 u  166 1024  377    0.386  -13.543   3.021


Warning: Output results may conflict during periods of changing synchronization.

TSJACS-SEDEPP1-01/acsadmin#

TSJACS-SEDEPP1-01/acsadmin# sh clock

Wed Jan 16 14:27:32 VET 2013

TSJACS-SEDEPP1-01/acsadmin# show logging application acs tail

acs Application log:

--------------------

==> /opt/CSCOacs/logs/ACSManagementAudit.log <==

Jan 16 2013 13:59:20 CisACS_52002 800 1 1 AUDIT Deleted configuration , inLocalMode=false, TransactionID=367, ObjectId=46, ObjectNam

e=fernando, AdminName=acsadmin, AdminInterface=GUI, ObjectType=Internal User, AdminSession=642D26D11145378422D27E2B0EFE35E7, AdminIP

Address=172.24.24.251

ACS Instance > ACS Configuration Audit

Administrator:

All

Object Type:

All

Object Name:

All

ACS Instance:

All

Show Local Mode Changes:

Yes

Show CTS Changes:

Yes

Date:

January 16, 2013

Generated on : January 16, 2013 2:06:24 PM VET

Logged At

Administrator

Interface

Object Type

Object Name

Event

Local Mode Change

ACS Instance

January 16,2013 2:29:20.293 PM acsadmin GUI Internal User fernando Deleted configuration No All

As you can see on the web gui: The DATE the info was generated was 2:06 PM and the log entry says 2:29PM.

And the NTP and the sh clock dont show any problems. And one thing that bothers me is that the same log in the server with " show logging application acs tail" command says the correct time "13:59:20".

HI ,

I am having also the same issue on ACS 5.2 with patch 7, I tried to Upgrade the patch from 7 to 11 but issue remains as it is. I configure timezone Asia/Kalkota( GMT+5.30 ) in logs timestamp is showing GMT time,i.e 5.30 hours behind normal clock.

Kindly reply....Thanks in advance

Regards,

Arvind.

hi Dulal,

Try to change Timezone from Asia/Kolkata to Asia/Calcutta and sync  ACS with NTP by Restarting ACS service.

Now I can able to see correct time on ACS reports.

try and check.

Regards,

Arvind.

Arvind: Good that you resolved the problem yourself. +5. Keep the good work.

Rating useful replies is more useful than saying "Thank you"

Rating useful replies is more useful than saying "Thank you"

I had faced the same problem with ACS 5.4. Changed the timezone to Asia/Calcutta.... Worked for me as welll.

Thanks at ton

Regards

Fazleabbas

Amjad Abdullah
Engager

Hi Dulal,

Make sure that you configure the time zone correctly as it is metnioned in the output of the command "show timezones".

Asia/Kolkata is available in the timezones.

Asia/Kalkota (that you use) is not available in the timezones.

Timezones have Asia/Calcutta as well. whatever correct timezone you choose is good. Just make sure you write it correctly.

After you make sure about that and configure the timestamp correctly then restart the ACS services:

application:

  command:  application stop acs

when the services stop then:

  commadn:  application start acs

wait until the servics come back up and that will probably resolve your issue.

HTH

Amjad

Rating useful replies is more useful than saying "Thank you"

Rating useful replies is more useful than saying "Thank you"
Content for Community-Ad