05-16-2017 11:46 PM
i have a strange issue.
running latest 126.96.36.199 AW, using vmware appliance.
hwclock is synced. cli shell date shows correct time. time-setup is set to UTC (we collect logs in UTC). NTP is configured for AW (although i'm not sure whether it can acually sync, there are no visible test options).
AW event logs show correct UTC time, but rapids is still living in its EDT time.
restarted AMP service (after clock sync), didn't help.
Solved! Go to Solution.
05-17-2017 01:42 AM
In AMP Setup > General>Dipsplay section set Timezone for UI Charts/Tables to UTC ,if it set to Browser local and check the status.
If my post addresses your query , give kudos:)
05-17-2017 02:34 AM
If my post helped you, don't forget to give kudos ;)
05-17-2017 03:52 AM - edited 05-17-2017 03:53 AM
already have Timezone for UI charts on UTC.
this affected home page/AP-devices/Connected clients etc visible charts but for some pequliar reason not RAPIDS->IDS events.
btw, just found out that syslogs & traps and reports are also showing time in EDT timezone.
for example, with UTC as AMP Setup-> General and System Defaults on Home-User Info. these events happened after any changes.
AW internal event log though (and usage/clients charts and tables) shows correct time.
05-17-2017 05:15 AM
Could you send below command output
# service ntpd status
-If you're utilizing NTP, then this will check to make sure that the service is running.
# ntpdate -u <ipaddr of ntp>
-This is a related NTP query which shows the offset jitter of the NTP server.
05-17-2017 05:23 AM - edited 05-17-2017 05:29 AM
[****@amper mercury]# date Wed May 17 12:21:19 UTC 2017 [****@amper mercury]# hwclock Wed 17 May 2017 12:21:22 PM UTC -0.719101 seconds [****@amper mercury]# service ntpd status ntpd (pid 2054) is running... [****@amper mercury]# ntpdate -u 188.8.131.52 17 May 12:21:28 ntpdate: adjust time server 184.108.40.206 offset -0.000115 sec
output from SSH to AW server
noting that i changed time-zone (using ./time-setup) some time after initial installation (although i've restarted AW afterwards).
05-17-2017 09:19 AM - edited 05-17-2017 09:22 AM
yes, timezone for groups (i'm using instant config mode) is UTC.
it seems that anything that is predefined report related (including RAPIDS reports) show time in EDT, but i see no way to change it.
all predefined reports (network usage, rf health etc) show their generation time in EDT. All reports under Definitions (where are predefined reports) are using EDT time.
i'm pretty sure i haven't put EDT anywhere, as i'm living in europe (actual timezone is EET or eastern european time).
for example, i can make a new generated report under Reports->Definitions, but for some reason it shows EDT as scheduling time option and no ways to change it.
i just took the screenshot, so the actual time when taken screenshot was 16:11 UTC. Why is shows Current Local Time in EDT is beyond me.
it was the same with previous 220.127.116.11 (just recently upgraded to 18.104.22.168).
even more strange: events under RAPIDS->Audit Log show UTC time (i think they are event logs), but events under RAPIDS->Events show EDT time.
05-17-2017 10:49 AM
May I know how did you set the timezone as UTC in Airwave? Could you map your timezone to localtime
sampe example below where we are mapping shanghai to localtime.
rm -rf /etc/localtime ln -s /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
05-17-2017 12:14 PM - edited 05-17-2017 12:17 PM
did what you provided, but no difference.
IIRC, there wasn't any time setup while OVA appliance install, just NTP configuration (and it's correctly showing under AW->AMP setup->General).
after that i saw that event log times did not match, but graphs were okay (default is local browser default i guess).
so i manually updated timezone, like here:
i also synched system clock using NTP and then synced hwclock with --systohc variable.
after that i restarted AW service.
amper install]# ./time-setup ------------------------ Date and Time Configuration --------------------- Current Time: Wed May 17 19:08:04 UTC 2017 1) Change Date and Time 2) Change Time Zone 0) Finish
so system clock itself is fine and also AW time for logging is fine. It's something deeper in AW generated reports, which doesn't want to take timezone into account and use instead some sort of default timezone (generated while installation i guess or come by default).
i haven't rebooted server itself (it's a production server after all, with over 100 connected AP-s), but i doubt it'll help