/srv/irclogs.ubuntu.com/2019/06/01/#ubuntu-server.txt

tomreyntelescopeemoji3: i don't, and wont be able to test, but it'd be easier for others to respond if you told which image exactly (ideally by download location) you used and which how-to you followed and how you determined that this image "updates to rpi2". also note there is #ubuntu-arm00:06
TJ-currently building nginx (finally) for Eoan00:17
tewardTJ-: that means you are about to fail randomly :P00:24
TJ-it's built, and installed, now I'm trying to restrict the container to 1 CPU although I'm not sure that'll help!00:30
TJ-argh, broken00:31
sdezielTJ-: once it started fine, you can try "service nginx upgrade" and see if systemd lost track of the new main PID00:31
sdezieloh shoot00:31
telescopeemoji3https://www.ubuntu.com/download/iot/raspberry-pi-2-3 im using the 3 image00:38
telescopeemoji3When it updates it changes the kernel to 200:38
telescopeemoji3oh nm00:38
telescopeemoji3i may be corrected00:39
telescopeemoji3uname -a00:39
telescopeemoji3Linux Raspberry 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux00:39
TJ-building again with added logging00:52
TJ-sarnold: nginx - do you know where the ngx_log_stderr() is supposed to go!? I'm not finding the output anywhere, even when starting nginx manually02:05
sarnoldTJ-: I do not :( it might require setting a specific loglevel somewhere..02:07
TJ-no, it seems somehow the debian build isn't including my code!02:10
TJ-I've added lots of ngx_log_stderr() with the string "child_pid" used, and "strings /usr/sbin/nginx" doesn't find it02:11
sarnoldstrings -a ?02:12
TJ-Aha! id' already done a fakeroot debian/rules build... so when I rebuilt the package it used the build products under ./debian/ ! Doing a 'clean' looks like it'll solve that02:14
TJ-so my adding log messages didn't get into the build products02:15
TJ-sarnold: we have data! https://paste.ubuntu.com/p/nksHVHcF2Q/02:29
sarnoldbeautiful!02:31
TJ-sarnold: patch is: http://paste.ubuntu.com/p/sMT3Wnj6pH/02:31
sarnoldTJ-: nginx[10421]:02:31
sarnoldTJ-: that never said 10422 :/02:32
TJ-so it seems like ngx_create_pidfile() is actually writing the /wrong/ pid into the file02:32
TJ-so becuase of how I've coded it it looks like I've got to 'munge' the ngx_pid02:33
TJ-building it now02:42
TJ-I hope this is it; been hacking away for 24 hours now02:44
TJ-sarnold: woohoo! https://paste.ubuntu.com/p/zrBPvhq4SR/03:03
sarnoldnginx[27728]: nginx: This should be child process PID 27729, parent PID 2772803:03
sarnoldTJ-: something's still goofy :(03:03
TJ-nah, it's fine03:04
TJ-systemd uses the parent PID in its logging regardless of child processes03:04
TJ-the funniest is "nginx[27728]: nginx: Process PID 27729 exiting" because that is printed after ngx_pid was set to the child PID :)03:05
TJ-but whereas before this the package installation would hang during configure, it didn't hang this time03:05
TJ-I'll remove the log messages and attach the patch to the bug03:06
sarnoldOH! so that part of the message isn't formatted by nginx? it's formatted by systemd? (and it gets it wrong, of course, becasuse why would it be doing the formatting.)03:06
TJ-well, I thought that was it, but just did a package upgrade and got this: "Jun 01 03:19:23 u1910 start-stop-daemon[18631]: /sbin/start-stop-daemon: warning: failed to kill -3: No such process"03:20
sarnoldoh my03:21
sarnoldwhy isn't there a process 3? I don't have one either :)03:21
sarnoldif that had been -2 or -4 or so on you might have had a bad day :)03:22
TJ-it's -3, NGX_BUSY, the tell-tale03:26
TJ-that's because when ngx_inherited == true ngx_daemon() is NOT called, so child_pid doesn't get set03:27
TJ-I've just got to add another test on ngx_inherited03:27
sarnoldthe thing is, kill with a negative pid number STILL KILLS -- process groups03:28
TJ-I've fixed that now, doing a build test03:35
TJ-this only affected reloads where there was no fork()03:36
TJ-sarnold: sorted, works perfectly for starts/stops/restarts03:46
TJ-attached to bug report, going to bed now03:46
sarnoldTJ-: beautiful! and .. the upgrade?03:46
sarnoldaha03:46
sarnoldTJ-: goodnight, good weekend :)03:46
TJ-yes, the upgrade too03:47
sarnold:D :D03:47
FarhaadNhi all07:32
FarhaadNi am using ubuntu server 12.04.5 LTS , and i know it's old, but i have problem on this07:33
FarhaadNdf not working07:33
lotuspsychjewe dont support eol versions FarhaadN07:33
lotuspsychjein this stage you can choose 12.04 ESM or !eolupgrade but reccomended would be clean install 16.04 or 18.0407:34
FarhaadNcan you help please from your experience?07:34
FarhaadNi cant upgrade server to newer version right now07:34
lotuspsychjeFarhaadN: supporting an eol version is not how it works, as your system might suffer all kinds of security flaws07:35
FarhaadNi know that , server isolate from security attack, i am just check mount and storage07:47
Greyztarcant seem to install packages no more is there a problem with the mirrors?15:21
Greyztarnvm was my iptables rules o.015:31
bandittiHello all.  I have a ubuntu server (18.04) with dual nic.  (10.0.0.0 and 10.0.100.0). I am trying to get one only to connect to a qnap box via iscsi.  when I use iscsiadm it logs in both IPs.  Also, need to figure out how to auto boot the mapping.  What am I missing?  Thank you in advance19:01

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!