pollen fails to log everytime rsyslog package is upgraded or daemon is bounced

Status changed to 'Confirmed' because the bug affects multiple users.

Since the update, it seems that pollen isn't logging anymore:

| -rw-r--r-- 1 syslog adm 276100 Nov 4 06:36 pollen.log-20141104.xz
| -rw-r--r-- 1 syslog adm 5665237 Nov 5 06:23 pollen.log-20141105
| -rw-r--r-- 1 syslog adm 703 Nov 5 23:23 pollen.log

| ubuntu@juju-machine-2-lxc-1:/var/log/pollen$ ps afxu | grep pollen
root 393 0.0 0.0 283676 12648 ? Ssl Aug05 33:22 /var/lib/juju/tools/unit-pollen-2/jujud unit --data-dir /var/lib/juju --unit-name pollen/2 --debug
| ubuntu 26609 0.0 0.0 8120 936 pts/0 S+ 23:25 0:00 \_ grep --color=auto pollen
pollen 26584 1.3 0.0 105380 3424 ? Ssl 23:23 0:01 pollen -http-port=80 -https-port=443 -device=/dev/random -bytes=64 -cert=/etc/pollen/cert.pem -key=/etc/pollen/key.pem

| ubuntu@juju-machine-2-lxc-1:/var/log/pollen$ tail pollen.log
| Nov 5 15:30:40 juju-machine-2-lxc-1 sudo: ubuntu : TTY=pts/0 ; PWD=/var/log/pollen ; USER=root ; COMMAND=/usr/sbin/service pollen restart
| Nov 5 15:30:40 juju-machine-2-lxc-1 pollen[17216]: pollen starting at [1415201440626942702]
| Nov 5 23:23:05 juju-machine-2-lxc-1 sudo: ubuntu : TTY=pts/0 ; PWD=/var/log/pollen ; USER=root ; COMMAND=/usr/sbin/service pollen restart
| Nov 5 23:23:05 juju-machine-2-lxc-1 pollen[26540]: pollen starting at [1415229785441503131]
| Nov 5 23:23:40 juju-machine-2-lxc-1 sudo: ubuntu : TTY=pts/0 ; PWD=/var/log/pollen ; USER=root ; COMMAND=/usr/sbin/service rsyslog restart
| Nov 5 23:23:40 juju-machine-2-lxc-1 pollen[26584]: pollen starting at [1415229820178875333]

I've decided not to accept the Utopic SRU of this until Haw's comment regarding it not logging anymore is addressed.

Hello Haw, or anyone else affected,

Accepted pollen into utopic-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/pollen/4.13-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Marking verification-failed due to comment #2.

Haw,

I can't reproduce your problem. Pollen is logging just fine here for me:

$ pollinate -t -s http://localhost:81
Jan 6 16:45:20 x230 pollinate[24365]: client sent challenge to
[http://localhost:81]
Jan 6 16:45:20 x230 pollinate[24410]: client verified
challenge/response with [http://localhost:81]
 |:�
    n뱠P��@;YQܶС+p�y9@$j(!h�j�
Jan 6 16:45:20 x230 pollinate[24420]: client hashed response from
[http://localhost:81]
Jan 6 16:45:20 x230 pollinate[24422]: client successfully seeded [-]

$ tail -f /var/log/syslog| grep pollen
Jan 6 16:43:51 x230 pollen[1393]: Server received challenge from
[127.0.0.1:57076, pollinate-testing/4.10-0ubuntu1
curl/7.37.1-1ubuntu3.1 Ubuntu/14.10
GNU/Linux/3.16.0-28-generic/x86_64] at [1420584231741378070]
Jan 6 16:43:51 x230 pollen[1393]: Server sent response to
[127.0.0.1:57076, pollinate-testing/4.10-0ubuntu1
curl/7.37.1-1ubuntu3.1 Ubuntu/14.10
GNU/Linux/3.16.0-28-generic/x86_64] at [1420584231742028522] in
[0.002116s]

:-Dustin

On Tue, Nov 18, 2014 at 11:37 AM, Launchpad Bug Tracker
<email address hidden> wrote:
> ** Branch linked: lp:ubuntu/utopic-proposed/pollen
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1386052
>
> Title:
> pollen fails to log everytime rsyslog package is upgraded or daemon is
> bounced
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1386052/+subscriptions

Ah right, so it seems logging location has changed from /var/log/pollen/pollen.log to /var/log/syslog.

Our pollen charm actually ships out an rsyslog config so it's logged to /var/log/pollen/pollen.log. I can confirm that with the latest updates, it's still logging to /var/log/syslog after rsyslog package update.

This bug was fixed in the package pollen - 4.13-0ubuntu1

---------------
pollen (4.13-0ubuntu1) utopic; urgency=medium

  * debian/pollen-restart.upstart, debian/pollen.upstart, debian/rules:
    - LP: #1386052
    - add a new upstart job that restarts pollen any time the rsyslog server
      is restarted
    - this is necessary to work around a bug in the golang syslog library
      where syslog restarts break logging
      + https://code.google.com/p/go/issues/detail?id=2264#c8
 -- Dustin Kirkland <email address hidden> Wed, 23 Jul 2014 00:08:55 -0700

The verification of the Stable Release Update for pollen has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Hello Haw, or anyone else affected,

Accepted pollen into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pollen/4.21-0ubuntu1~14.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

The fix for this bug has been awaiting testing feedback in the -proposed repository for trusty for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository.