[15:42] <N3sh108> hello, I am trying to use upstart for my nodejs server but I just get 'stop/waiting'
[15:42] <N3sh108> the upstart script should be correct though
[15:44] <N3sh108> is that a normal behaviour?
[16:14] <JanC> you get stop/waiting but your nodejs server is still running?
[16:17] <JanC> in that case the upstart job config is not correct
[16:18] <N3sh108> JanC: I went through it and fixed some problems. Now I get: start/running, process XXX
[16:18] <N3sh108> but the server doesn't work
[16:20] <N3sh108> any idea JanC?
[16:20] <JanC> is the nodejs server actually running?
[16:21] <N3sh108> nope
[16:22] <JanC> seems like the nodejs server doesn't start then?
[16:22] <JanC> or starts and immediately exits or crashes?
[16:22] <N3sh108> let me check
[16:23] <JanC> (I've never used nodejs, so no idea what might go wrong)
[16:23] <N3sh108> ok
[16:23] <N3sh108> if I run my exec command myself
[16:23] <N3sh108> it works
[16:24] <N3sh108> but now when I either start it manually (start <program>) or when I reboot the machine
[16:25] <N3sh108> I don't get why
[16:26] <N3sh108> arggg
[16:26] <N3sh108> wasting so much time
[16:28] <JanC> a web search gave me this: https://github.com/cvee/node-upstart  (not sure if it's useful for you?)
[16:30] <JanC> there are some other articles to be found too, which do things somewhat differently
[16:32] <N3sh108> still nothing
[16:32] <N3sh108> fuck this shit
[16:32] <N3sh108> 1 hour wasted for nothing
[16:35] <JanC> BTW: when it works when you run it from the command line, but not from an upstart job, then usually the problem is something in the "environment" that is different (e.g. environment variables, working directory, application expects a tty, etc.)
[16:35] <JanC> also, permissions
[17:48] <N3sh108> thanks, it magically fixed itself :D
[18:54] <JanC> possibly it was still confused by a previous test without rebooting?


[02:24] -ubottu:#ubuntu-news- ::fridge:: Ubuntu Weekly Newsletter Issue 810 @ https://fridge.ubuntu.com/2023/10/23/ubuntu-weekly-newsletter-issue-810/
[03:30] -ubottu:#ubuntu-news- ::planet:: Ubuntu Blog: The winter is coming, and so is the Ubuntu Summit @ https://ubuntu.com//blog/the-winter-is-coming-and-so-is-the-ubuntu-summit
[03:30] -ubottu:#ubuntu-news- ::planet:: Ubuntu Blog: Meet Canonical at SC23 @ https://ubuntu.com//blog/meet-canonical-at-sc23
[03:30] -ubottu:#ubuntu-news- ::planet:: The Fridge: Ubuntu Weekly Newsletter Issue 810 @ https://fridge.ubuntu.com/2023/10/23/ubuntu-weekly-newsletter-issue-810/
[03:34]  * guiverc has updated scripts & re-running has the items now automatically (what I added manually)  thanks krytarik & apologies for missing update
[04:19] <Bashing-om> guiverc: 811 off and running on Discourse - how is the head ache ?
[04:20] <guiverc> still annoying, i'm a 'walking zombie'... but hey i'm walking
[04:23] <Bashing-om> guiverc: There is that :P - beats some alternatives that come to mind. // whenever your mind gets clear there is Mastodon's Ubuntu NewsLetter bot that we can gain control of. Open to discussion.
[04:25] <guiverc> yeah i noted discussion but have NOT thought about it (in no hurry for anything currently)
[04:27] <Bashing-om> guiverc: Understandable - I too have not had the time to look and think :) On my get-2-it list however :D
[12:15] -ubottu:#ubuntu-news- ::omg!ubuntu:: Firefox 119 Lets You Add Images to PDFs, Import Chrome Extensions @ https://www.omgubuntu.co.uk/2023/10/firefox-119-lets-you-add-images-to-pdfs-import-chrome-extensions


[17:40] <bdmurray> nuclearbob: Do you have any upgrade testing to Yakkety going on?
[17:40] <nuclearbob> bdmurray: yep. There's a bug installing policykit, I'll find it for you
[17:42] <nuclearbob> bdmurray: if you want, I can also give you information on the url where all the upgrade testing runs, for future reference, but I'm always happy to give you the results when I'm around as well
[17:42] <bdmurray> nuclearbob: the url would be nice too
[17:42] <nuclearbob> bdmurray: this is the current bug I have: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1614576
[17:43] <nuclearbob> I'm working on documentation for the jobs on the wiki here: https://wiki.canonical.com/UbuntuEngineering/QA/JenkinsJobs/UpgradeTesting
[17:45] <bdmurray> nuclearbob: Is this crash recreatable?
[17:46] <nuclearbob> bdmurray: yes, every time I run the an upgrade, automatically or if I manually recreate the test process.  Would you rather run the automated code, or have instructions to do the same stuff?
[17:47] <bdmurray> nuclearbob: I think instructions if its not too much trouble.
[17:48] <nuclearbob> bdmurray: sure, I'll email them to you shortly
[17:48] <nuclearbob> I may have already put them on that wiki page, let me check
[17:50] <nuclearbob> bdmurray: try this on a xenial system: http://paste.ubuntu.com/23276051/
[17:50] <nuclearbob> sorry, should all be sudo
[17:50] <nuclearbob> pulled from the tests here: http://bazaar.launchpad.net/~canonical-platform-qa/auto-upgrade-testing/autopkgtest/view/head:/debian/tests/upgrade#L369
[17:52] <bdmurray> nuclearbob: also for future reference subscribing me to bugs might be best (if they aren't about ubuntu-release-upgrader)
[17:52] <nuclearbob> bdmurray: will do, thanks for letting me know
[19:35] <nuclearbob> ubuntu-qa: is anybody having problems with autopilot autolandings? I'm investigating some other landing problems, and working on a good long-term fix, but I can apply a short term one if anyone needs to get unblocked