Timestamp in log doesn't change

[Usman Malik]

Version: gearmand 1.1.3

Timestamp in logging doesn't change when using --verbose INFO. It remains the same (as the time last service was last started).

In example below, the timestamp is always "2013-05-20 20:53:58.000000 " which was the time server was started.

 NOTICE 2013-05-20 20:53:58.000000 [ proc ] accepted,api_log,b60e8d61-4e88-4642-a819-67af10136518,0 -> libgearman-server/server.cc:297
   INFO 2013-05-20 20:53:58.000000 [ 3 ] Peer connection has called close() 10.185.1.150:34593
   INFO 2013-05-20 20:53:58.000000 [ 3 ] Disconnected 10.185.1.150:34593
   INFO 2013-05-20 20:53:58.000000 [ 3 ] Gear connection disconnected
   INFO 2013-05-20 20:53:58.000000 [ main ] Accepted connection from 10.185.3.151:41751
   INFO 2013-05-20 20:53:58.000000 [ 2 ] Gear connection made
 NOTICE 2013-05-20 20:53:58.000000 [ proc ] accepted,api_log,61d80d48-9c3a-40f7-8725-c8fcf1371153,0 -> libgearman-server/server.cc:297
   INFO 2013-05-20 20:53:58.000000 [ 2 ] Peer connection has called close() 10.185.3.151:41751
   INFO 2013-05-20 20:53:58.000000 [ 2 ] Disconnected 10.185.3.151:41751
   INFO 2013-05-20 20:53:58.000000 [ 2 ] Gear connection disconnected

[Brian Aker (brianaker)]

Try trunk

Sent from my Ti85

On May 20, 2013, at 14:05, Usman Malik <email address hidden> wrote:

> Public bug reported:
>
> Version: gearmand 1.1.3
>
> Timestamp in logging doesn't change. It remains the same (as the time
> last service was last started)
>
> In example below, the timestamp is always "2013-05-20 20:53:58.000000 "
> which was the time server was started.
>
> NOTICE 2013-05-20 20:53:58.000000 [ proc ] accepted,api_log,b60e8d61-4e88-4642-a819-67af10136518,0 -> libgearman-server/server.cc:297
> INFO 2013-05-20 20:53:58.000000 [ 3 ] Peer connection has called close() 10.185.1.150:34593
> INFO 2013-05-20 20:53:58.000000 [ 3 ] Disconnected 10.185.1.150:34593
> INFO 2013-05-20 20:53:58.000000 [ 3 ] Gear connection disconnected
> INFO 2013-05-20 20:53:58.000000 [ main ] Accepted connection from 10.185.3.151:41751
> INFO 2013-05-20 20:53:58.000000 [ 2 ] Gear connection made
> NOTICE 2013-05-20 20:53:58.000000 [ proc ] accepted,api_log,61d80d48-9c3a-40f7-8725-c8fcf1371153,0 -> libgearman-server/server.cc:297
> INFO 2013-05-20 20:53:58.000000 [ 2 ] Peer connection has called close() 10.185.3.151:41751
> INFO 2013-05-20 20:53:58.000000 [ 2 ] Disconnected 10.185.3.151:41751
> INFO 2013-05-20 20:53:58.000000 [ 2 ] Gear connection disconnected
>
> ** Affects: gearmand
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to
> Gearman.
> https://bugs.launchpad.net/bugs/1182228
>
> Title:
> Timestamp in log doesn't change
>
> Status in Gearman Server and Client Libraries:
> New
>
> Bug description:
> Version: gearmand 1.1.3
>
> Timestamp in logging doesn't change. It remains the same (as the time
> last service was last started)
>
> In example below, the timestamp is always "2013-05-20 20:53:58.000000
> " which was the time server was started.
>
> NOTICE 2013-05-20 20:53:58.000000 [ proc ] accepted,api_log,b60e8d61-4e88-4642-a819-67af10136518,0 -> libgearman-server/server.cc:297
> INFO 2013-05-20 20:53:58.000000 [ 3 ] Peer connection has called close() 10.185.1.150:34593
> INFO 2013-05-20 20:53:58.000000 [ 3 ] Disconnected 10.185.1.150:34593
> INFO 2013-05-20 20:53:58.000000 [ 3 ] Gear connection disconnected
> INFO 2013-05-20 20:53:58.000000 [ main ] Accepted connection from 10.185.3.151:41751
> INFO 2013-05-20 20:53:58.000000 [ 2 ] Gear connection made
> NOTICE 2013-05-20 20:53:58.000000 [ proc ] accepted,api_log,61d80d48-9c3a-40f7-8725-c8fcf1371153,0 -> libgearman-server/server.cc:297
> INFO 2013-05-20 20:53:58.000000 [ 2 ] Peer connection has called close() 10.185.3.151:41751
> INFO 2013-05-20 20:53:58.000000 [ 2 ] Disconnected 10.185.3.151:41751
> INFO 2013-05-20 20:53:58.000000 [ 2 ] Gear connection disconnected
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gearmand/+bug/1182228/+subscriptions