/srv/irclogs.ubuntu.com/2018/10/16/#ubuntu-server.txt

=== cpaelzer_ is now known as cpaelzer
cpaelzergood morning04:40
lordievaderGood morning06:03
cpaelzerhiho lordievader06:20
lordievaderMorning cpaelzer06:20
lordievaderHow are you doing?06:20
cpaelzergood, and you?06:21
lordievaderDoing good here :)06:21
cpaelzerglad to hear that06:21
GargoyleHey there. If I manually remove a package with "apt remove some-package" does this prevent it from being installed again automatically in the future? (I now see it listed in dpkg --get-selections with "deinstall")07:40
GargoyleI'm trying to recreate a scenario where php7.2 seems to have been, allegedly, automatically upgraded to 7.3RC.07:41
DenBeirenfor some reason one of my machines is in read only filesystem.08:20
DenBeirenI guess there should be a forcefsck run on reboot08:20
DenBeirenis there a way to make it reboot and check?08:20
hateballDenBeiren: differs a bit depending on your version08:22
DenBeirenlatest,.. 18.04.108:22
hateballDenBeiren: you'd need to change kernel parameters to force08:23
hateballthat said, systemd should notice it has failed and run an fsck itself08:24
hateballDenBeiren: are all partitions mounted ro ?08:25
hateballDenBeiren: basically these are your options https://www.freedesktop.org/software/systemd/man/systemd-fsck@.service.html08:26
DenBeirenthe problem is that i have no options editing or creating any files08:37
DenBeirensince i am stuck in read only mode08:37
cpaelzer_DenBeiren: those are kernel commandline options consumed by systemd08:43
cpaelzer_DenBeiren: you can set them from grub or whatever your bootloader is08:43
cpaelzer_disk being readonly isn't preventing you to do that08:43
DenBeireni'm afraid i don't understand what i should do,.. never had/did this before :s08:50
hateballDenBeiren: do you have physical access to the server?08:50
hateballby physical I mean can you interupt the boot process and get into grub08:50
DenBeirenno, not now,.. alls is done trough ssh08:50
hateballDenBeiren: is your /boot partition also mounted ro ?08:53
DenBeirenhttps://pastebin.com/biu1d2cM08:56
DenBeirenhttps://pastebin.com/yFKNs7sX08:59
hateballDenBeiren: run "mount |grep sda"09:01
hateballthat should how /boot is currently mounted. if you can mount it rw, you can edit /boot/grub/grub.cfg manually to force fsck next reboot09:02
=== cpaelzer_ is now known as cpaelzer
DenBeiren/boot/grub/grub.cfg is empty,... is that ok?09:51
DenBeirenoops09:51
DenBeireni was wrong09:51
DenBeirenhow should i edit grub? where and what?09:53
blackflowDenBeiren: looking at the context of the convo above, it appears you should edit that grub.cfg with any text editor and add fsck.mode=force to the vmlinuz kernel command line09:54
blackflowDenBeiren: in the first "menuentry 'Ubuntu' ....."  section, there's "linux" line above "initrd", at the bottom of the { } group. The "linux" line is the kernel command line.09:56
blackflowAdd that fsck.mode=force at the end of that line, save the file, umount /boot and reboot09:56
DenBeirenhere goes nothing ;-)09:57
DenBeirenin beaver we trust :-)09:58
hateballfamous last words, it would seem10:11
GargoyleI didn't think you were supposed to edit grub.cfg manually anymore?10:37
blackflowGargoyle: you aren't. the user couldn't get to root and had the option to mount /boot separately for that one tiem fix and boot regularly.10:55
blackflow(being a remote server with no accses to grub menu itself)10:55
DenBeirennot last words hateball :-)11:45
DenBeirenit rebooted but i can't say for sure if it did the check11:45
DenBeirenmy errors aren't gone in any case11:45
blackflowDenBeiren: but did you manage to boot regularly?11:48
DenBeirenit rebooted and came back up,..11:49
DenBeireni'm not there with the machine to check the monitor11:49
blackflowwhat errors then?11:49
DenBeirenfor example when i want to edit a file, sudo nano /etc/"tabkey" it gives me the following11:50
DenBeirenhttps://pastebin.com/jeSQMWLN11:51
blackflowDenBeiren: pastebin   mount | grep tmp     please?11:53
Ussat\o/ Xwiki server upgraded from 16.x --> 18.x11:53
DenBeirenhttps://pastebin.com/CaEiW5yY11:54
blackflowDenBeiren: and what about just `mount`, no grep?11:55
DenBeirenhttps://pastebin.com/Am0f9gLd11:56
blackflowDenBeiren: try   mount -o -remount,rw /11:56
blackflowDenBeiren: also please pastebin your /etc/fstab11:57
GargoyleDo you have any kind of message in dmesg suggesting why / is being mounted ro?11:58
DenBeirenhttps://pastebin.com/CahVM1Bx12:01
blackflow"floppy:"  !!!12:03
Gargoyleext2 !!!12:04
GargoyleHow old is this machine?12:04
GargoyleLooks like it's a VM too. Do you control the hypervisor?12:05
blackflowDenBeiren: can you pastebin fstab?   Looks like something is not remounting root rw after root pivot.12:05
Ussatext2...wow12:06
hateballit's not *that* long ago since ext2 was default on /boot if you installed with LVM :p12:08
blackflowLooks like Bionic according to uname12:09
DenBeirenhttps://pastebin.com/PqSxrNLL12:10
blackflowDenBeiren: typo on line 7? looks like no root mount in fstab, and that initial ro is never remounted12:12
Gargoyleis line 7 a copy and paste error?12:12
blackflowDenBeiren: hit enter after <pass>   on line 712:13
blackflowalso............ floppy? really?12:13
hateballdont copy that floppy12:13
DenBeirenhey, it's standard :-)12:20
DenBeireni guess12:20
blackflowwhat!12:20
DenBeireni can't edit the file,..12:20
blackflowDenBeiren: did you run that remount?12:20
blackflowof course you didn't. you users never read the support advice you ask for.       mount -o remount,rw /              and then you can edit stuff freely. edit fstab, fix line 7 and reboot for test. you're welcome.12:21
DenBeirenblackflow: of course i did,.. but the level of knowledge with us n00bs is never as high as you guys might expect ;-)12:22
blackflowyou can always ask if something is not clear. that's what support is for ;)12:24
GargoyleDenBeiren: Show us the remount command and the output.12:25
DenBeireni was able to edit, found the typo and waiting to login after reboot atm12:25
Gargoyleah. ok12:25
DenBeirenyep! seems like that did the trick guys and gals,..12:26
DenBeirenthx a lot for the help!12:30
ahasenackrbasak: hi, I have an sru question13:12
ahasenackI'm working on a fix for a bug, and it has been fixed in bionic+ already13:12
ahasenackrbasak: the fix I intend to apply to trusty and xenial is from upstream and is simpler13:12
ahasenackrbasak: but different from what is applied to bionic+13:12
rbasakI think that's fine13:13
rbasakAs long as there isn't expected to be a user visible functional regression on upgrade13:13
ahasenackrbasak: the bionic one comes from debian, so changing that to the upstream one (better and simpler) adds to delta,13:13
ahasenackrbasak: and the debian fix relies on a config change, so backing that out now would mean another config change13:13
ahasenackrbasak: so I think leaving bionic alone is best at this time13:14
rbasakThat sounds right to me13:14
rbasakProbably good to explain in the SRU description what you just said though.13:14
ahasenackagreed13:14
v0lksmanhey all!  trying to figure out how to remove all packages installed from a particular source13:27
v0lksmanrunning `grep Package: /var/lib/apt/lists/archive_name_*_Package but it's listing packages that aren't currently installed13:28
rbasakv0lksman: use dpkg-query to get a list of installed packages. Then xargs over "dpkg -s" or similar to look for Source:. grep-dctrl might be useful. If there is no Source: header, the source package name is the same as the binary package name.13:42
sdezielv0lksman: less elegant an possibly showing some false positives but I usually use that: for p in $(dpkg -l | awk '/^ii/ {print $2}'); do apt-cache policy "$p" | grep -qF "ppa.launchpad.net/foo" && echo "$p"; done13:49
Ussatubuntu 12.......srsly.....he is running 1213:54
* Ussat cries13:54
v0lksmanthanks guys...looking at options.13:56
v0lksmanUssat: hope that wasn't directed at me13:56
Ussatno, it was not13:56
sdeziel12.04 is still supported via ESM so there is still a chance was not left there rotting13:59
ahasenackcpaelzer: I think I can add dep8 tests to that backuppc package15:00
ahasenackrbasak: in terms of an sru, adding a dep8 that doesn't exist in the development release, is that a no-no?15:00
ahasenackrbasak: scenario is bionic+ has the fix, but no dep8, and I'm adding the fix *and* a dep8 test for it to trusty and xenial15:00
ahasenackit's just the dep8 fix that isn't in the distros I'm not touching15:01
rbasakahasenack: I think an upload to Cosmic (or Cosmic+1 as needed) to add the dep8 would be appreciated.15:04
ahasenackrbasak: sure, but would it block the sru?15:04
rbasakI wouldn't block an SRU just because Cosmic is frozen and therefore you can't add the dep8 righ tnow.15:04
ahasenackrbasak: I'm thinking weeks until that could happen15:04
ahasenackok15:04
ahasenackthat would be my intention, sorry for not making it clear. I would definitely add the dep8 test to c+1 when it opens15:04
rbasakPerhaps you could leave the upload for cosmic+1 ready somewhere and link to it in the bug, and explain that you can't do it now due to freeze?15:05
ahasenacksure15:06
ahasenackwhat about the releases in the middle?15:06
rbasakBut yeah if you agree to put it in later, it doesn't make sense to me to block the SRU.15:06
ahasenackbionic and cosmic itself15:06
rbasakWhat is it, tough SRU question day today? :)15:06
ahasenackI've done an sru in the past which was about fixing an *existing* dep8 test, but not one to add one15:06
ahasenacksure :)15:06
rbasakI won't make you do the releases in the middle given that you've said the issue doesn't affect them.15:06
ahasenackok, as I thought :)15:07
ahasenackI'll still see how tough adding the dep8 test will be, but from what I've seen just by writing the testing instructions, all that can be scripted easily15:08
* rbasak tries to be pragmatic about these things; if the underlying reasons for a policy look like a bad trade-off, let's skip the policy :)15:08
rbasak(in a specific case for specific reasons only, of course; otherwise the policy should be questioned/changed first)15:08
tewardrbasak: i saw your reply, and sarnold's on that bug.  It's a bit late in the Cosmic cycle to add that, so it'll get added in Dd-series15:18
teward(nginx --with-compat)15:18
sam_wrbasak: we're having some preseed issues with 14.04, install completes fine but apt is left in a funky state due to shim: https://www.irccloud.com/pastebin/2uSLUZYU/ manually upgrading dpkg to 1.17.5ubuntu5.8 over 1.17.5ubuntu5 works... is this something we'll just have to add as a postinstall task or something or is there a better fix?15:20
rbasaksam_w: not sure why you're asking me?15:27
rbasaksam_w: that's interesting though. You do need the newer dpkg from trusty-updates first it seems if you want to install other things from trusty-updates. I'm not sure what mechanism exists (if any) to make sure that dpkg is updated before attempting to install shim.15:27
rbasaksam_w: is the newer dpkg available in the same apt repository? IOW are you using a custom hacked mirror or something, or the official upstream repositories there?15:28
tewardrbasak: wasn't that a known upgrade-blocker a long time ago in the 14.04 -> 16.04 blocker there?15:28
tewardi coulda sworn we had some kind of upgrade-blocking evil like that at that cycle15:28
rbasakI don't remember, but it would affect release upgrades too I think.15:28
sam_wrbasak: I think kierank was talking to you about it the other day? Apologies if not!15:29
rbasaksam_w: I remember a conversation about preseeding and hacking an apt repository but not about shim!15:34
rbasaksam_w: conclusion in #ubuntu-devel is that it's a bug. Please could you file one against shim, and tag it "regression-update"?15:34
sam_wrbasak: no hacked mirror, it's just in trusty-updates15:34
sam_wrbasak: sure15:35
rbasakYeah I'm told it should declare a Pre-Depends, and doesn't, for some complicated reasons due to how it got there.15:35
=== jelly-home is now known as jelly
ahasenackhm, with bileto, do I need one ticket per ubuntu release?18:36
ahasenacklooks like yes18:36
ahasenackeven though a ppa can hold packages for multiple releases18:36
RoyK!bileto18:44
ahasenackRoyK: https://wiki.ubuntu.com/Bileto18:48
ahasenackand bileto.ubuntu.com18:48
xnoxahasenack, it's the best recommended practice, yes. one ticket per ubuntu release.19:25
xnoxmulti-release publish is hard19:26
ahasenackI don't use it for publishing, just running dep8 tests in all arches and also the dependent tests19:38
RoyKxnox: it should be easy if a ticket could be marked with all relevant releases19:38

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