| === fluter is now known as Mode | ||
| === Mode is now known as fluter | ||
| === fluter_ is now known as fluter | ||
| === JanC_ is now known as JanC | ||
| === DingoSaar_ is now known as DingoSaar | ||
| Orm_Ancalagon | Evening all, if this is not the right place to ask i apologise and would be greatful for directions to it. I have a couple of questions regarding upstart order for initialising services if anyone could give a few pointers? | 19:36 |
|---|---|---|
| JanC | Orm_Ancalagon: any questions about upstart are welcome here, but the channel is very quiet generally | 19:38 |
| Orm_Ancalagon | That’s most kind | 19:39 |
| JanC | also, make sure to read the manpages & the cookbook | 19:39 |
| JanC | also, so /topic for a link to the mailing list | 19:39 |
| JanC | *see* | 19:39 |
| Orm_Ancalagon | Cool | 19:39 |
| Orm_Ancalagon | I am having a little difficulty with two services on Ubuntu server 14.04 and their start order | 19:40 |
| Orm_Ancalagon | I have an XMPP server called Prosody which I configured to use MYSQL for its database | 19:41 |
| Orm_Ancalagon | I changed it from SQL lite since I wanted to support password hashing | 19:41 |
| Orm_Ancalagon | Anyway | 19:41 |
| Orm_Ancalagon | On first boot, I think prosody gets started before MYSQL and hence fails | 19:41 |
| Orm_Ancalagon | There’s a error log noting “can’t connect to MYSQL database" | 19:42 |
| JanC | sounds like that, yeah | 19:42 |
| Orm_Ancalagon | However, once the sytem is booted, restarting prosody spools up just fine | 19:42 |
| Orm_Ancalagon | Is there a way to make Prosody check MYSQL is up and running before starting? | 19:43 |
| Orm_Ancalagon | Or perhaps a delay I could set against it | 19:43 |
| JanC | how is prosody started right now? | 19:43 |
| Orm_Ancalagon | It’s daemonised and configured to start on boot following the apt-get install | 19:44 |
| Orm_Ancalagon | I’ve had a read through the cookbook, but I am quite newbish at this level | 19:45 |
| Orm_Ancalagon | And must admit i’ve never really needed to poke at init before | 19:45 |
| JanC | I mean, is it started by an upstart config or using a sysvinit script? | 19:46 |
| JanC | is there a /etc/init/prosody.conf ? | 19:48 |
| Orm_Ancalagon | you know what i’m being dum | 19:48 |
| Orm_Ancalagon | the /etc/init is upstart and /etc/init.d is sysvinit isn’t it | 19:49 |
| Orm_Ancalagon | there’s no prosody.conf in /etc/init but it is in /etc/init.d/prosody | 19:49 |
| JanC | okay, so that complicates things a bit, I guess :) | 19:50 |
| Orm_Ancalagon | Heh | 19:50 |
| Orm_Ancalagon | I note mysql actually appears in both /etc/init and /etc/init.d | 19:51 |
| Orm_Ancalagon | So does Ubuntu combine by sysvinit scripts and upstart for starting services then? | 19:53 |
| JanC | the mysql one in init.d is not a real sysvinit script (it's there for compatibility with some other software, I guess) | 19:53 |
| Orm_Ancalagon | Ah ok | 19:53 |
| JanC | and upstart can start/stop/etc. sysvinit scripts for backwards compatibility | 19:54 |
| JanC | like the prosody one | 19:54 |
| Orm_Ancalagon | ah that’s why a sudo service restart prosody works | 19:54 |
| Orm_Ancalagon | I see | 19:54 |
| JanC | I'm not 100% sure what is the "right way" to make a sysvinit script wait on mysql though... | 19:57 |
| Orm_Ancalagon | Yeah I wonder, given the mixture, if it might be possible to set a delay on sysvinit start for prosdy | 19:58 |
| Orm_Ancalagon | in order to avoid complication | 19:58 |
| JanC | maybe best would be to make a prosody.conf for it :) | 20:01 |
| Orm_Ancalagon | wow is that possible? | 20:01 |
| Orm_Ancalagon | Jan thanks for you help, it was most appreciated, i’m going to have a play at writing a .conf | 21:58 |
| Orm_Ancalagon | Hope you have a great day | 21:58 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!