Re: Gunicorn init script
On Tue, Jan 21, 2014 at 06:41:04AM -0500, Philippe Clérié wrote: > On 01/21/2014 03:38 AM, Andrei POPESCU wrote: > >On Lu, 20 ian 14, 15:28:33, Henning Follmann wrote: > >> > >>Yes, > >>in Wheezy bootlogd is active by default. In previous versions you had to > >>enable it by setting > >>BOOTLOGD_ENABLE=yes > >>in /etc/default/bootlogd > >> > >>The boot messages will be logged to /var/log/boot > > > >True, but since it's Priority: optional it might not be installed at > >all. > > > >Kind regards, > >Andrei > > > > Ignore my previous message. > > When I started the VM this morning, bootlogd did register several > error lines from gunicorn. Seems it cannot change to the source > directory of one of the sites it's serving. That particular > directory is on a NFS share. See, that would be information which should be included in your first post. Initially I thought about network issues. Here I use Cisco catalyst switches. And the port take up to 10 seconds to come up. This can cause issues with network services during boot. > > I am going to assume that, on cold boots, when gunicorn starts, NFS > mounts are incomplete because it takes the VM time to get the low > level stuff settled. On warm boots, that work is done, so NFS mounts > complete before gunicorn starts. :-) It's a working hypothesis! > > (Of course that does not explain why bootlogd showed nothing yesterday.) > Well, lets assume that was PEBKAC ;) > But thanks for the suggestions! > -H -- Henning Follmann | hfollm...@itcfollmann.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140121135449.gc12...@newton.itcfollmann.com
Re: Gunicorn init script
On 01/21/2014 03:38 AM, Andrei POPESCU wrote: On Lu, 20 ian 14, 15:28:33, Henning Follmann wrote: Yes, in Wheezy bootlogd is active by default. In previous versions you had to enable it by setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd The boot messages will be logged to /var/log/boot True, but since it's Priority: optional it might not be installed at all. Kind regards, Andrei Ignore my previous message. When I started the VM this morning, bootlogd did register several error lines from gunicorn. Seems it cannot change to the source directory of one of the sites it's serving. That particular directory is on a NFS share. I am going to assume that, on cold boots, when gunicorn starts, NFS mounts are incomplete because it takes the VM time to get the low level stuff settled. On warm boots, that work is done, so NFS mounts complete before gunicorn starts. :-) It's a working hypothesis! (Of course that does not explain why bootlogd showed nothing yesterday.) But thanks for the suggestions! -- Philippe -- The trouble with common sense it that it is so uncommon. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52de5cd0.3000...@gcal.net
Re: Gunicorn init script
On 01/21/2014 03:38 AM, Andrei POPESCU wrote: On Lu, 20 ian 14, 15:28:33, Henning Follmann wrote: Yes, in Wheezy bootlogd is active by default. In previous versions you had to enable it by setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd The boot messages will be logged to /var/log/boot True, but since it's Priority: optional it might not be installed at all. Kind regards, Andrei It wasn't. Plus even when started gunicorn leaves no traces in /var/log/boot. -- Philippe -- The trouble with common sense it that it is so uncommon. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52de4f8b.9050...@gcal.net
Re: Gunicorn init script
On Lu, 20 ian 14, 15:28:33, Henning Follmann wrote: > > Yes, > in Wheezy bootlogd is active by default. In previous versions you had to > enable it by setting > BOOTLOGD_ENABLE=yes > in /etc/default/bootlogd > > The boot messages will be logged to /var/log/boot True, but since it's Priority: optional it might not be installed at all. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Gunicorn init script
On Mon, Jan 20, 2014 at 02:48:12PM -0500, Philippe Clérié wrote: > On 01/20/2014 01:20 PM, Henning Follmann wrote: [...] > > Nothing in syslog or messages. Nothing in gunicorn logs, not even a > trace that it attempted to start. And on boot, the init script > message from gunicorn is barely visible long enough before the > screen is cleared for the login prompt; I get a glimpse of it on > reboot, but not on cold boot. > > Is there a way to make the init process more verbose? > > -- > Philippe > Yes, in Wheezy bootlogd is active by default. In previous versions you had to enable it by setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd The boot messages will be logged to /var/log/boot HTH -H -- Henning Follmann | hfollm...@itcfollmann.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140120202833.gb12...@newton.itcfollmann.com
Re: Gunicorn init script
On 01/20/2014 06:44 PM, Philippe Clérié wrote: > I have a strange problem with Gunicorn on Debian Wheezy. Using Debian > init scripts, it does not start on a cold boot but works just fine if > started manually or on a warm reboot. > > Any ideas what could cause that? > > Yeah, compare the environments. I'll bet the init scripts missing some essential stuff for gunicorn. Cheers Frank -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52dd8141.3050...@dead-link.org
Re: Gunicorn init script
On 01/20/2014 01:20 PM, Henning Follmann wrote: On Mon, Jan 20, 2014 at 12:44:35PM -0500, Philippe Clérié wrote: I have a strange problem with Gunicorn on Debian Wheezy. Using Debian init scripts, it does not start on a cold boot but works just fine if started manually or on a warm reboot. Any ideas what could cause that? -- Philippe -- The trouble with common sense it that it is so uncommon. Well, common sense should tell you to look at the log. The information provided nobody can help you with your problem. -H Sorry. :-) Not common sense. Automatic reflexes. Nothing in syslog or messages. Nothing in gunicorn logs, not even a trace that it attempted to start. And on boot, the init script message from gunicorn is barely visible long enough before the screen is cleared for the login prompt; I get a glimpse of it on reboot, but not on cold boot. Is there a way to make the init process more verbose? -- Philippe -- The trouble with common sense it that it is so uncommon. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52dd7d7c.3020...@gcal.net
Re: Gunicorn init script
On Mon, Jan 20, 2014 at 12:44:35PM -0500, Philippe Clérié wrote: > I have a strange problem with Gunicorn on Debian Wheezy. Using > Debian init scripts, it does not start on a cold boot but works just > fine if started manually or on a warm reboot. > > Any ideas what could cause that? > > > -- > Philippe > > -- > The trouble with common sense it that it is so uncommon. > > > Well, common sense should tell you to look at the log. The information provided nobody can help you with your problem. -H -- Henning Follmann | hfollm...@itcfollmann.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140120182024.ga12...@newton.itcfollmann.com
Gunicorn init script
I have a strange problem with Gunicorn on Debian Wheezy. Using Debian init scripts, it does not start on a cold boot but works just fine if started manually or on a warm reboot. Any ideas what could cause that? -- Philippe -- The trouble with common sense it that it is so uncommon. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52dd6083.70...@gcal.net
