SmartZone bug with timezones

jeff_roback — Sat, 16 Dec 2017 17:50:10 GMT

There appears to be a bug with timezones in the AP's connected to a SmartZone controller. If you have the timezone of a zone set to anything except GMT, there will be log entries every 90 seconds that say the following:

wsgclient/timezone value too big: PST+8PDT

Since this is happening every 90 seconds, you end up with thousands of these. I'm seeing this in the AP support logs under the ### RPM Log ### section.

At first I thought this was an error of it not liking PST+8PDT which I had originally chosen for my Smart Zone's timezone, but I found that if you pick any timezone, you'll get a similar result. Basically anything except GMT seems to cause this.

I'm not sure if this has any functional effect on the AP at this point beyond the log spew and associated CPU required to generate it..... .but it doesn't seem like a good thing.

I did mention this to tech support, and they explained to me that I'm in a different timezone than they are... so I dropped it. But I wanted to post it in here in the hopes that someone from Ruckus could have a look and determine if this is a problem.

At the moment I'm not sure if it's best to just switch all our AP's to use GMT and do the conversion in my head (which I'm not especially good at) or just leave it be and scroll past them when reviewing logs..

Here's an example from one of my AP's. This particular AP had 2,500 like this, but it does look like that section of the log loops itself at that point. So perhaps no harm other than making the logs hard to look through.

### RPM Log ###
Nov 28 05:13:29 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:14:59 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:16:29 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:18:00 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:19:29 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:20:59 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:22:29 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:23:59 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c30
Nov 28 05:25:29 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c30
Nov 28 05:26:59 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:28:29 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:29:59 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:31:29 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:32:59 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68
Nov 28 05:34:29 RPM ERR @ PID:1011:rpm.c:rpm_get:1440 wsgclient/timezone value too big: PST+8PDT,M3.2.0/02:00,M11.1.0/02:00(35)[max=20]. xact=0x1db4c68

Re: SmartZone bug with timezones

jakob_peterh_ns — Mon, 18 Dec 2017 08:56:12 GMT

I did mention this to tech support, and they explained to me that I'm in a different timezone than they are... so I dropped it.

Sometimes, it's simply amazing what responses you get from 1. level support.. it's like they don't read what's written right in front of them 😕

Re: SmartZone bug with timezones

martin_martin — Mon, 18 Dec 2017 09:50:34 GMT

Hi Jeff,

Can you let me know the case number while you had contact with support I will check it.

As background info.
The controller and the AP's run internal on GMT timezone only the Webpart can be made user timezone set.

This is done to keep a clear overview in the log files.

Regards
Martin

topic Re: SmartZone bug with timezones in Access Points - Indoor and Outdoor

SmartZone bug with timezones

Re: SmartZone bug with timezones

Re: SmartZone bug with timezones