| golinux | Aaaarrrrrgh . . . I decided to update Chimaera in synaptic and it's stuck at Unpacking firefox-esr (115.15.0esr-1~deb11u1) over (115.14.0esr-1~deb11u1) ... | 02:48 |
|---|---|---|
| golinux | what do I do? | 02:49 |
| gnarface | stuck how? is it just taking a long time or is there an error? | 02:49 |
| golinux | I rarely play with my Devuan internals these days and don't remember this ever happening before. | 02:50 |
| golinux | No error. Just blinking cursor | 02:50 |
| golinux | It has been maybe 5 minutes | 02:51 |
| gnarface | sometimes my downloads go to 0b/s for long periods during updates, and synaptic might not give you any indication of that | 02:51 |
| fsmithred | I think therer's a way to open a terminal in synatpic | 02:51 |
| gnarface | it might be an upstream issue, is what i'm saying | 02:51 |
| golinux | Everything is downloaded.It is trying toinstall | 02:52 |
| fsmithred | should be a button that says Show More or something like that | 02:52 |
| golinux | and is stuck | 02:52 |
| gnarface | hmm, need an error, yes. you could try it again with apt-get to see if that's got more useful output | 02:53 |
| gnarface | synaptic and apt use the same cache directory don't they? | 02:53 |
| golinux | I will have to close the window that has the install info and start from the beginning, I guess | 02:54 |
| gnarface | if apt-get uses the same cache directory it won't have to redownload everything | 02:55 |
| fsmithred | I can't do an upgrade to see what you're supposed to click on because I'm all upgraded | 02:55 |
| gnarface | unfortunately i don't use synaptic very much, so i'm not sure about that though | 02:55 |
| golinux | This is the window with the terminal output of the installation that is stuck | 02:55 |
| fsmithred | yeah, terminal. Any relevant messages there? | 02:55 |
| golinux | Unpacking distro-info-data (0.51+devuan2) over (0.51+devuan1) ... | 02:56 |
| golinux | Preparing to unpack .../3-firefox-esr_115.15.0esr-1~deb11u1_amd64.deb ... | 02:56 |
| golinux | Leaving 'diversion of /usr/bin/firefox to /usr/bin/firefox.real by firefox-esr' | 02:56 |
| golinux | Unpacking firefox-esr (115.15.0esr-1~deb11u1) over (115.14.0esr-1~deb11u1) ... | 02:56 |
| golinux | \ | 02:56 |
| gnarface | outta ram or disk space? | 02:57 |
| golinux | Last lines and now a blinking cursor | 02:57 |
| golinux | No way | 02:57 |
| fsmithred | check it anyway | 02:58 |
| fsmithred | df -h | 02:58 |
| gnarface | "iotop -a" could tell you if it's still currently writing or reading any data to/from the disk, but at some point they changed the kernel build so you have to have "delayacct" in the kernel command-line for that to work right... not sure if that was before chimaera or not | 02:59 |
| golinux | $ df -h | 03:00 |
| golinux | Filesystem Size Used Avail Use% Mounted on | 03:00 |
| golinux | udev 3.9G 0 3.9G 0% /dev | 03:00 |
| golinux | tmpfs 783M 868K 782M 1% /run | 03:00 |
| golinux | tmpfs 5.0M 4.0K 5.0M 1% /run/lock | 03:00 |
| golinux | tmpfs 3.2G 0 3.2G 0% /dev/shm | 03:00 |
| golinux | tmpfs 783M 8.0K 783M 1% /run/user/1000 | 03:00 |
| fsmithred | we didn't really need every line | 03:00 |
| gnarface | "free -m" will tell you if you're outta swap or not... i've seen some weird issues with certain types of memory leaks that would use up all the swap then that would in turn implicitly throttle updates down to a pinhole... just throwing out guesses here | 03:01 |
| fsmithred | just / and /home if you have it | 03:01 |
| golinux | Well I have no idea which onee you do nedd | 03:01 |
| fsmithred | or any line that has more than 90% | 03:01 |
| gnarface | hmm... also, if there's a physical problem with the disk itself, the output of dmesg should be choked with some errors after a certain timeout... | 03:02 |
| gnarface | (though sometimes these can also be false positives caused by really slow normal writes) | 03:02 |
| golinux | / is using 19 of 34 gb | 03:03 |
| fsmithred | ok rule out disk space | 03:04 |
| golinux | / home is using 58 of 423 gb | 03:05 |
| fsmithred | dmesg | 03:06 |
| fsmithred | or dmesg | tail | 03:06 |
| golinux | This is a bit long | 03:07 |
| golinux | $ dmesg | tail | 03:07 |
| golinux | [944075.227742] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out | 03:07 |
| golinux | [944075.227744] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out | 03:07 |
| golinux | [944075.229265] ata5.00: configured for UDMA/100 | 03:07 |
| golinux | [944077.569754] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) | 03:07 |
| golinux | [944077.675727] ata1.00: configured for UDMA/133 | 03:07 |
| fsmithred | I think you get a minute timeout | 03:08 |
| gnarface | golinux: send it to termbin or paste.debian.net | 03:08 |
| fsmithred | oh good. I really didn't feel like looking up the commands. | 03:10 |
| fsmithred | nc termbin.com 9999 < some-file | 03:10 |
| golinux | Thing is I closed all my browsers before the upgrade so have to deal with that | 03:10 |
| fsmithred | some-command | nc termbin.com 9999 | 03:10 |
| golinux | I am just going to close synaptic and ==try again | 03:11 |
| golinux | Ha! It is non-responsive!! | 03:12 |
| golinux | Maybe I should kill it? | 03:12 |
| gnarface | maybe... what does your "Swap" line say in the output of "free -m" though? | 03:13 |
| golinux | phone? | 03:13 |
| fsmithred | terminal | 03:13 |
| golinux | xkill or something else? | 03:14 |
| fsmithred | free -m | 03:15 |
| gnarface | so, maybe just kill it and try it again, but for the issue of diagnosis we still would need more data, because i've seen this type of thing caused by anything from failing harddrives to failing power supplies to a nvidia driver memory leak | 03:15 |
| golinux | New PS is only a few months old | 03:15 |
| gnarface | and if it's PATA, the failing drive might not even be the one in use currently! | 03:15 |
| golinux | HD always passes the test but haven't done it in a while | 03:16 |
| golinux | I have 2 disks in the box | 03:16 |
| golinux | sata | 03:16 |
| golinux | WD black | 03:16 |
| gnarface | i should amend that; failing or below-spec power supply. like, say you added a few harddrives and upgraded the video card, the power supply may be perfectly good but just not sufficient to power everything at once anymore, if it's not rated to however many watts you're drawing | 03:17 |
| gnarface | usually such a situation though is also hinted at by intermittent boot failures | 03:17 |
| golinux | I never touch my hardware unless it fails and Wes come to pick it up and fix it. | 03:17 |
| golinux | I only reboot after an upgrade otherwise suspend | 03:19 |
| golinux | I killed it | 03:20 |
| golinux | Behaving for the machine is not a life. | 03:21 |
| Xenguy | I would ditch synaptic and resume with the command-line equivalent, but fsmithred and gnarface probably know better | 03:21 |
| fsmithred | as in "know about herding cats" | 03:22 |
| golinux | I used to do it that way but too lazy in my old age . . . | 03:22 |
| Xenguy | For me it's the opposite, I'm too lazy to use synaptic : -P | 03:23 |
| golinux | Wit a few decades! | 03:23 |
| golinux | Wait | 03:23 |
| Xenguy | Were you just trying to do a general update golinux ? | 03:24 |
| Xenguy | And synaptic got stuck? | 03:24 |
| fsmithred | yeah, it looked like it choked on firefox | 03:24 |
| Xenguy | So maybe, as root, just run: apt-get update && apt-get upgrade -s | 03:25 |
| Xenguy | ? | 03:25 |
| golinux | Tried to restart synaptic and apt is still running. | 03:25 |
| golinux | I need to kill it. | 03:25 |
| Xenguy | pkill synaptic | 03:25 |
| Xenguy | pkill apt | 03:26 |
| Xenguy | lather rinse repeat | 03:26 |
| golinux | What is the -s at the end of the apt command ? I never used that | 03:27 |
| fsmithred | if those don't work, then pkill -9 whatever | 03:27 |
| fsmithred | --simulate | 03:27 |
| golinux | Already pkilled | 03:27 |
| Xenguy | Yeah, '-s' says just simulate what's going to upgrade | 03:28 |
| Xenguy | Like a preview | 03:28 |
| golinux | Ah . . . of course . . . | 03:28 |
| golinux | Xenguy saves the day! That seemed to work!! | 03:29 |
| golinux | Now without the "s"? | 03:29 |
| Xenguy | Now just: apt-get upgrade | 03:30 |
| golinux | In process . . . | 03:30 |
| golinux | I am having flashbacks of when I actually used to like playing with the machine | 03:31 |
| Xenguy | "In the beginning was the command-line..." | 03:31 |
| gnarface | so, it occurs to me that the other thing that is virtually indistinguishable after-the-fact from the case of failing harddrive or failing power supply, is a brown-out at the power outlet | 03:33 |
| golinux | There are errors but will litharge slap me again? | 03:33 |
| Xenguy | paste.debian.net | 03:33 |
| gnarface | ...and in theory, enough directed RF interference could also cause a similar type of choke, but that's fairly rare while the brown-out thing is increasingly common these days | 03:34 |
| fsmithred | nc termbin.com 9999 < some-file | 03:34 |
| Xenguy | netcat, that's cooooooooooool | 03:34 |
| fsmithred | pr | 03:34 |
| fsmithred | or | 03:34 |
| golinux | All browsers closed atm all present on at least 5 desktops if I open one | 03:35 |
| gnarface | (which is why i've had to put put all my computers and even my freaking home theater setup on UPS now) | 03:35 |
| fsmithred | some-command | nc termbin.com 9999 | 03:35 |
| golinux | gnarface: I did that decades ago | 03:35 |
| fsmithred | I once called the power company to ask why the window fan slowed down at the same time the lights got brighter, and they couldn't answer. | 03:36 |
| Xenguy | haha | 03:36 |
| golinux | E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 10321 (dpkg) | 03:36 |
| fsmithred | But my neighbor explained that they play with the cycles and give you less power. I don't really understand the explanantion | 03:36 |
| fsmithred | kill 10321 | 03:36 |
| fsmithred | uh | 03:37 |
| fsmithred | wait | 03:37 |
| golinux | They say not to remove it | 03:37 |
| fsmithred | is that dpkg in the middle of installing a downloaded package? | 03:37 |
| golinux | Yes | 03:37 |
| golinux | Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? | 03:37 |
| golinux | IT is hung. | 03:37 |
| golinux | How about a reboot. | 03:37 |
| Xenguy | I'd probably just damn the torpedos and kill that process | 03:38 |
| Xenguy | as root | 03:38 |
| fsmithred | yeah | 03:38 |
| Xenguy | kill -9 10321 | 03:38 |
| fsmithred | don't reboot now | 03:38 |
| golinux | N: Be aware that removing the lock file is not a solution and may break your system. | 03:38 |
| Xenguy | yeesh | 03:38 |
| Xenguy | I find that hard to believe | 03:38 |
| golinux | That was terminal output | 03:39 |
| fsmithred | maybe that depends on which package is half-upgraded | 03:39 |
| golinux | Is it safe to reboot? | 03:39 |
| fsmithred | I would kill the process before rebooting | 03:39 |
| Xenguy | But I'm impetuous sometimes; I'd probably kill the process and trust that apt-get is smart enough to resume where it left off | 03:39 |
| fsmithred | if you reboot you WILl be killing the process | 03:39 |
| golinux | I already killed synaptic. | 03:39 |
| Xenguy | yes, hold off on rebooting | 03:40 |
| golinux | And just closed the terminal | 03:40 |
| Xenguy | What do you think fsmithred : kill -9 10321 | 03:40 |
| Xenguy | ? | 03:40 |
| golinux | Maybe that will undo the lock | 03:40 |
| Xenguy | I imagine you need to explicitly kill that process | 03:41 |
| fsmithred | you didn't try that already? | 03:41 |
| Xenguy | This is actually a fascinating use case | 03:41 |
| fsmithred | oh, yeah -9 | 03:41 |
| Xenguy | Not used to seeing such a thing | 03:41 |
| fsmithred | silver bullet | 03:41 |
| Xenguy | for werewolve processes : -) | 03:42 |
| fsmithred | wooden stake? | 03:42 |
| fsmithred | oh, salt for zombies | 03:42 |
| golinux | This waning says not to: | 03:42 |
| Xenguy | "Stab me in the heart Big Eddie!" | 03:42 |
| golinux | N: Be aware that removing the lock file is not a solution and may break your system. | 03:42 |
| Xenguy | I don't believe that, but understand if you're hesitant | 03:43 |
| fsmithred | which ps command will show wtf dpkg is doing? | 03:43 |
| Xenguy | ps aux |grep dpkg | 03:43 |
| Xenguy | or: pgrep dpkg | 03:44 |
| golinux | Which one guys | 03:44 |
| golinux | ? | 03:44 |
| * Xenguy defers to fsmithred ... | 03:44 | |
| Xenguy | I don't want to be the 'too many cook' in the kitchen, just trying to help along the way | 03:45 |
| fsmithred | first one | 03:45 |
| * golinux shoots daggers at FF | 03:45 | |
| golinux | # ps aux |grep dpkg | 03:46 |
| golinux | root 10321 0.0 1.5 125960 122248 ? Ds 19:40 0:01 /usr/bin/dpkg --status-fd 32 --no-triggers --unpack --auto-deconfigure --force-remove-protected --recursive /tmp/apt-dpkg-install-KY76wt | 03:46 |
| golinux | root 12295 0.0 0.0 6240 712 pts/0 S+ 20:45 0:00 grep dpkg | 03:46 |
| fsmithred | this cook is about to clock out and go to sleep | 03:46 |
| Xenguy | weeeeeeeeee | 03:46 |
| golinux | Noooo! | 03:46 |
| Xenguy | It that same rogue process again: 10321 | 03:47 |
| golinux | Translate that output please | 03:47 |
| Xenguy | Well, I think we need to kill that process number 10321 | 03:48 |
| Xenguy | And at this point I'd be 'by hook or by crook', despite the dire warnings | 03:48 |
| golinux | Warning that it could break things | 03:48 |
| fsmithred | apt-dpkg-install-KY76wt <- what is that? | 03:48 |
| fsmithred | in /tmp | 03:48 |
| golinux | I have no idea. | 03:49 |
| Xenguy | Yeah well, sometimes you gotta break eggs to make an omelette | 03:49 |
| fsmithred | less /tmp/apt-dpkg-install-KY76wt see if you can read it | 03:49 |
| Xenguy | In my experience apt-get and dpkg are usually fairly robust in terms of their ability to recover from interupted processes | 03:50 |
| golinux | # less /tmp/apt-dpkg-install-KY76wt | 03:50 |
| golinux | /tmp/apt-dpkg-install-KY76wt is a directory | 03:50 |
| golinux | 03:50 | |
| fsmithred | you should put that in the terminal and do not put the output here | 03:50 |
| fsmithred | look inside it | 03:50 |
| Xenguy | I get the impression some upgrade process somehow got hung, and now it's time to end that and rerun things on the command-line, but that's just a guess of course | 03:51 |
| fsmithred | yeah, I was hoping to verify that it was firefox or some other unimportant program | 03:52 |
| Xenguy | good idea | 03:52 |
| Xenguy | look in the directory | 03:52 |
| golinux | I won't let me open it | 03:53 |
| Xenguy | Get root | 03:53 |
| golinux | Hahahah! | 03:54 |
| * golinux misses gtksu | 03:55 | |
| golinux | I have no idea how to do that these days | 03:55 |
| fsmithred | su - | 03:55 |
| fsmithred | less /tmp/apt-dpkg-install-KY76wt | 03:56 |
| Xenguy | Then enter the root password | 03:56 |
| fsmithred | ls /tmp/apt-dpkg-install-KY76wt | 03:56 |
| Xenguy | If you need gtksu you're doing it wrong ; -) | 03:57 |
| golinux | There are 8 lines | 03:57 |
| Xenguy | pick a pastebin? | 03:58 |
| gnarface | golinux: you don't have /tmp mounted as tmpfs, do you? (it would have said so in the output of "df -h") | 03:58 |
| Xenguy | I'm guessing doubtful? | 03:58 |
| golinux | I put the output into a pm Xengut and fsr | 03:59 |
| fsmithred | I see a couple of those that might be a problem | 03:59 |
| golinux | gnarface: I wouldn't know how to do that . . . | 04:00 |
| gnarface | i do recall running into one particular issue while upgrading chimaera, where if /tmp is mounted with the noexec option, it chokes while unpacking a kernel package, because said package tries to exec a shell script it just extracted to /tmp... which doesn't require /tmp to be mounted tmpfs but is for some reason common in the configs of people who do | 04:00 |
| gnarface | i've only seen kernel packages do that, but in theory other packages could | 04:00 |
| gnarface | ...and it seems to be particularly bad behavior by many accounts, but there we are | 04:01 |
| gnarface | maybe something similar went wrong with something in /tmp here | 04:01 |
| gnarface | but instead of throwing an error it just hung, i guess? | 04:01 |
| Xenguy | https://paste.debian.net/hidden/6d07f408/ | 04:02 |
| gnarface | maybe because of synaptic.. | 04:02 |
| golinux | Thanks Xenguy | 04:02 |
| Xenguy | Just kill it and start over with apt-get, that's my 'damn the torpedos' advice | 04:02 |
| golinux | fsmithred? | 04:02 |
| * Xenguy wanders off blindly... | 04:03 | |
| gnarface | yea, i suppose i'd second Xenguy's advice | 04:03 |
| golinux | Nooooo! | 04:03 |
| fsmithred | Yeah, I would have done it long ago. | 04:03 |
| gnarface | if apt-get also fails, maybe it'll be more obvious why, and if it doesn't, i'd probably just blame it on synaptic and then toss synaptic overboard | 04:04 |
| fsmithred | good advice | 04:04 |
| Xenguy | kill kill kill | 04:04 |
| golinux | Could someone please repaste the command? | 04:04 |
| gnarface | though if it can be provably isolated to synaptic, maybe it'd warrant a bug report... | 04:04 |
| Xenguy | kill -9 10321 | 04:04 |
| Xenguy | as root | 04:04 |
| golinux | Hopefully it won't explode | 04:10 |
| Xenguy | Blow it sky high | 04:10 |
| golinux | Hopefully see you on the other side . . . | 04:10 |
| Xenguy | : -) | 04:10 |
| gnarface | just make sure you have a kernel and udev (or eudev) still installed if you reboot before finishing the upgrade... | 04:10 |
| Xenguy | No need to reboot | 04:10 |
| Xenguy | Just kill the existing instance, and then try again with apt-get | 04:10 |
| golinux | Nothing exploded. | 04:10 |
| golinux | Now let me try the uograde again | 04:10 |
| Xenguy | So what happens if you try again: apt-get update && apt-get upgrade -s | 04:10 |
| Xenguy | ? | 04:10 |
| Xenguy | And if that looks clean: apt-get upgrade | 04:10 |
| Xenguy | mwuhaha | 04:10 |
| golinux | Tried to upgrade after doing that and still getting the same error | 04:10 |
| Xenguy | This is too much, I need another beer | 04:10 |
| Xenguy | Fortunately linux and beer usually go quite well together = ) | 04:11 |
| golinux | Are you sure that kill -9 10321 is correct? | 04:11 |
| fsmithred | pgrep dpkg | 04:12 |
| golinux | # pgrep dpkg | 04:13 |
| golinux | 10321 | 04:13 |
| fsmithred | then yes, the above command is correct | 04:13 |
| Xenguy | Talk about a rogue process, can it not be killed? | 04:13 |
| golinux | It isn't working | 04:13 |
| fsmithred | there's a lock file? | 04:13 |
| golinux | I have run kill -9 10321 several times | 04:14 |
| golinux | Yes | 04:14 |
| Xenguy | That's not possible, kill -9 10321 should kill it dead, and if not then I'd just resign myself to rebooting | 04:14 |
| fsmithred | then I guess it needs to be removed | 04:14 |
| Xenguy | Then try apt-get update again | 04:15 |
| fsmithred | I don't remember where they are | 04:15 |
| golinux | Just did and uit failed | 04:15 |
| fsmithred | var/run or run? | 04:15 |
| Xenguy | I think it was: /tmp/apt-dpkg-install-KY76wt | 04:15 |
| Xenguy | Maybe remove the directory forcibly? | 04:16 |
| golinux | # /tmp/apt-dpkg-install-KY76wt is a directory | 04:17 |
| Xenguy | Yeah, so removing it is still an option | 04:17 |
| Xenguy | removing it and its contents I suppose | 04:17 |
| fsmithred | what's in /var/lock? | 04:18 |
| Xenguy | Either that or just rebooting, which would likely accomplish the same thing | 04:18 |
| golinux | bash: /var/lock: Is a directory | 04:18 |
| fsmithred | yes it is | 04:18 |
| fsmithred | what's in it? | 04:18 |
| Xenguy | ls /var/lock | 04:19 |
| fsmithred | anything having to do with dpkg maybe? | 04:19 |
| fsmithred | btw, I don't really know wtf I'm doing | 04:19 |
| Xenguy | Who does, I've only been running linux since the 90's : -P | 04:19 |
| Xenguy | I try not to reboot unless I have to (point of pride) but sometimes that will do the trick = ) | 04:20 |
| golinux | /var/lock asound.state.lock | 04:23 |
| fsmithred | not that one | 04:23 |
| fsmithred | is that the only file? | 04:23 |
| golinux | And an lvm directory | 04:24 |
| Xenguy | If it were me: just fucking reboot, tear it all down, and build it up again | 04:24 |
| fsmithred | lsof |grep dpkg | 04:24 |
| golinux | and some thing re gkrellm | 04:24 |
| golinux | dpkg 10321 root 3uW REG 8,1 0 1059086 /var/lib/dpkg/lock-frontend | 04:26 |
| golinux | dpkg 10321 root 4uW REG 8,1 0 1059085 /var/lib/dpkg/lock | 04:26 |
| golinux | dpkg 10321 root 5w REG 8,1 | 04:26 |
| fsmithred | I guess you need to remove /var/lib/dpkg/lock-frontend | 04:27 |
| golinux | It is a long list | 04:27 |
| fsmithred | all related to dpka? | 04:27 |
| golinux | I can put it in a pm | 04:27 |
| fsmithred | ok | 04:27 |
| fsmithred | just get rid of the lock file | 04:29 |
| fsmithred | rm /var/lib/dpkg/lock-frontend | 04:29 |
| golinux | OK | 04:29 |
| golinux | Done . . . supposedly . . . | 04:30 |
| fsmithred | then pkill -9 10321 | 04:30 |
| golinux | OK | 04:30 |
| fsmithred | apt -s upgrade | 04:31 |
| fsmithred | or apt-get if you prefere | 04:31 |
| Xenguy | kill -9 10321 | 04:33 |
| golinux | E: Could not get lock /var/lib/dpkg/lock. It is held by process 10321 (dpkg) | 04:33 |
| golinux | N: Be aware that removing the lock file is not a solution and may break your system. | 04:33 |
| golinux | E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? | 04:33 |
| fsmithred | yeah, right | 04:33 |
| Xenguy | Kick that process in the nuts, right now | 04:34 |
| golinux | Are we on a moebius strip in time? | 04:34 |
| Xenguy | = ) | 04:34 |
| Xenguy | There's doubtless a way to do it without rebooting (this is linux after all), but rebooting might just return everything to a sane state, from which you can progress from there | 04:35 |
| fsmithred | is the lock file still there? | 04:36 |
| golinux | fsmithred ? | 04:36 |
| golinux | Yes | 04:36 |
| fsmithred | the file you removed | 04:36 |
| fsmithred | ls /var/lib/dpkg/lock-frontend | 04:36 |
| golinux | 10321 | 04:36 |
| fsmithred | huh? | 04:37 |
| golinux | E: Could not get lock /var/lib/dpkg/lock. It is held by process 10321 (dpkg) | 04:37 |
| golinux | N: Be aware that removing the lock file is not a solution and may break your system. | 04:37 |
| golinux | E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? | 04:37 |
| golinux | Same message over and over | 04:37 |
| fsmithred | yeah, that message suggests that the lock file still exists | 04:38 |
| fsmithred | I am asking you to use the ls command to see if it lists that file in that directory | 04:38 |
| golinux | Ya think? LOL! | 04:38 |
| fsmithred | ie. does the file still exist? | 04:38 |
| fsmithred | ls /var/lib/dpkg/lock-frontend | 04:38 |
| fsmithred | yes or no? | 04:39 |
| fsmithred | no such file or directory | 04:39 |
| fsmithred | ^^^ that's what is should say | 04:39 |
| golinux | /var/lib/dpkg/lock-frontend | 04:40 |
| golinux | still there with 0 bytes in it | 04:40 |
| golinux | Bigger hammer? | 04:41 |
| fsmithred | but no error message when you delete it??? | 04:41 |
| golinux | No | 04:41 |
| fsmithred | I guess reboot | 04:41 |
| golinux | Ok | 04:41 |
| fsmithred | or wait for someone who knows more | 04:41 |
| golinux | At least we have phone if reboot fails | 04:43 |
| fsmithred | I'm not staying up all night fixing a computer over the phone | 04:44 |
| golinux | Xenguy? | 04:44 |
| golinux | Tomorrow is another day . . . | 04:44 |
| fsmithred | leave it alone and go to sleep | 04:44 |
| fsmithred | don't reboot now | 04:44 |
| golinux | OK. | 04:45 |
| fsmithred | g'night | 04:45 |
| golinux | Thanks for your time and patience . . . | 04:45 |
| golinux | You too! | 04:46 |
| gnarface | so, i've only seen it happen once when not related to some hardware i/o glitch, but there was a weird situation where a process could crash in some way that would leave it stalled and unresponsive even to "kill -9" but essentially only at that point consist of a mostly empty directory of the form /proc/[pid], which you could just manually delete to fully eliminate the process | 05:22 |
| gnarface | i think that was supposed to have been fixed long ago in a kernel patch though | 05:22 |
| gnarface | sometimes there's still a long delay after the "kill -9" for it to work though | 05:23 |
| gnarface | in all other situations, typically this means it's stalled waiting for some hardware i/o operation to complete, which might be indicative of a driver problem | 05:23 |
| golinux | Thanks gnarface . . . I am cooked for the night. | 05:26 |
| golinux | Everything has been working fine. Can | 05:27 |
| golinux | 't remember ever having a snafoo like this. | 05:27 |
| golinux | I don't muck around in my system so have no idea what happened . . . | 05:28 |
| golinux | See you tomorrow | 05:29 |
| gnarface | could have been sunspots, who knows? without more data points, there's not much we can do about it anyway | 05:41 |
| adhoc | gnarface: sun spots, i am sure there is a deck of cards for your rolodex to spin through any time you need an excuse =) | 05:47 |
| adhoc | that reminds me, I wonder if they have published anything in recent times... ? | 05:48 |
| golinux | gnarface: I can't suspend. I did logout and back in but the problem remains. System is acting really weird. | 05:59 |
| gnarface | weird... | 06:01 |
| gnarface | is this something using nvidia video cards and drivers by any chance? | 06:01 |
| gnarface | their stuff tends to come with gremlins | 06:01 |
| golinux | Nope | 06:06 |
| golinux | No non-free | 06:07 |
| golinux | I hate to leave it running all night but fsmithred said to leave it alone until tomorrow . . . | 06:08 |
| golinux | Please leave any thoughts here or with fsmithred as I am off to bed and you will be there yourself before I wake up. | 06:19 |
| gnarface | golinux: oh, ok. just thought of another one; misbehaving input device. like, sometimes a USB device goes crazy and starts effectively fuzzing the kernel, and you might see weird behavior. if you have any spare unused USB devices maybe try unplugging them, or at least checking to see if they're working normally | 06:51 |
| gnarface | i've seen that cause Xorg specific issues too, that manifested as certain windows/panels freezing up, easily becoming a red herring for a graphical issue | 06:52 |
| gnarface | this one time it just turned out to be that my mouse right-scroll "click" state had gotten digitally stuck into the on position | 06:53 |
| gnarface | hotplugged it and the problem went away | 06:53 |
| al1r4d | good afternoon | 07:03 |
| onefang | adhoc: No need for a deck of cards, there's the fortune-bofh-excuses package. B-) | 09:19 |
| adhoc | onefang: oh nice =) | 09:21 |
| adhoc | to be fair, i preferred the spin the rolodex option myself =) | 09:22 |
| adhoc | has the tactile randomness to it... | 09:22 |
| golinux | gnarface: No usb devices | 12:26 |
| tempforever | I've had process that 'kill -9' as root wouldn't kill off, before. I didn't look in /proc/<pid> but will keep that in mind if it occurs in the future. I just rebooted, problem was solved. It was a while back, don't remember what the process was anymore. | 14:50 |
| tempforever | But yeah, looking at the dpkg pastebin it doesn't appear any of those are potentially system-breaking packages, a reboot should be fine (if dpkg can't be killed) | 14:52 |
| devuanconsumer | I am mining on several computers and need to setup remote connections to those computers. How can I set this up on devuan? Last time I tried I wasn't able to do it successfully | 15:38 |
| devuanconsumer | thank you | 15:38 |
| devuanconsumer | I am also using a router VPN as well | 15:39 |
| avir327 | install openssh-server, or dropbear? | 15:49 |
| al1r4d | openssh | 16:27 |
| Xenguy | golinux, So did that locked file 'process won't die' situation get resolved at all? | 21:29 |
| golinux | Yes! Took about 2.5 hours | 21:45 |
| Xenguy | golinux, What was the solution, generally? | 21:56 |
| freem | Hi. There is a missing and important info on https://www.devuan.org/os/documentation/install-guides/daedalus/bookworm-to-daedalus | 23:45 |
| freem | it does not gives the name of the debug symbols proxy | 23:45 |
| freem | I tried to guess various names, but so far without any success | 23:45 |
| freem | some of the variants I tried, as I don't remember them all: | 23:46 |
| freem | deb http://deb.devuan.org/merged-debug daedalus-debug main contrib non-free-firmware | 23:46 |
| freem | deb http://deb.devuan.org/merged daedalus-debug main contrib non-free-firmware | 23:46 |
| rrq | not sure what you are talking about, or why. | 23:47 |
| freem | programs have debugging symbols which are stripped in debian, moved into specific packages which are useless for normal users but very important for developpers | 23:48 |
| freem | https://wiki.debian.org/DebugPackage | 23:48 |
| freem | and I need them because I'm contributing to open source softwares | 23:49 |
| freem | https://wiki.debian.org/AutomaticDebugPackages | 23:49 |
| freem | note that I do NOT let stuff install packages automatically on my system, but when I was on debian this was not a problem, as I knew how to install those I need | 23:50 |
| freem | https://wiki.debian.org/SourcesList#Debug_Symbol_Packages | 23:50 |
| freem | I would love it if debian could stop moving those each release though | 23:51 |
| freem | it's annoying as fuck to update the stuff every 2 years... but at least they have the stuff documented | 23:51 |
| rrq | here are debians repositories: https://ftp.debian.org/debian/dists/ | 23:51 |
| freem | yes, debian ones | 23:52 |
| freem | except I moved to deVUan recently, and the doc does not mentions how to get this | 23:52 |
| rrq | get what? | 23:52 |
| freem | and devuan does recompiles some libs. A mismatching pair of lib/dbgsym would just cost me many, many hours of headaches, so I can not use debian's repos for that | 23:53 |
| rrq | get what? | 23:53 |
| freem | I want to have dbgsym packages *from a devuan repo* since devuan mirrors *some* (most) of debian's | 23:53 |
| freem | debug symbols for the 4th time | 23:53 |
| freem | they are contained in packages | 23:53 |
| rrq | they are not repositories; they are packages | 23:53 |
| freem | which are in a specific location | 23:53 |
| freem | this location is a repo | 23:54 |
| freem | I want to know which repo, on devuan, contains them | 23:54 |
| rrq | usually siblings to the packages | 23:54 |
| freem | yes, indeed, but they are NOT in the same repo, to avoid polluting users with them by accident or something | 23:54 |
| rrq | try again | 23:55 |
| rrq | they are siblings to their packages | 23:55 |
| freem | what do you mean by siblings? | 23:56 |
| rrq | they have same name as their packages followed by "-dbgsym" | 23:56 |
| freem | I want to know devuan's equivalent of "deb http://deb.debian.org/debian-debug/ bookworm-debug main | 23:56 |
| freem | " | 23:56 |
| freem | yes, I know | 23:56 |
| freem | I have debian's dbgsym installed, already | 23:56 |
| rrq | there is no such repository point | 23:57 |
| freem | but I want to update them so that I can be certain the problem I'm debugging is not related to a mismatch | 23:57 |
| freem | ok | 23:57 |
| freem | so it means devuan does not exposes the debug symbols at all | 23:57 |
| rrq | the debug symbol package for package xxxx is named xxx-dbgsym | 23:57 |
| rrq | the debug symbol package for package xxxx is named xxxx-dbgsym | 23:57 |
| rrq | devuan does what debian does | 23:58 |
| freem | so devuan merged them in a single repo? | 23:58 |
| rrq | devuan does what debian does | 23:58 |
| freem | which means it needs a separate repo | 23:58 |
| freem | which is not documented anywhere I could find | 23:58 |
| rrq | no that it doesn;t | 23:58 |
| rrq | the debug symbol package for package xxxx is named xxxx-dbgsym | 23:58 |
| freem | please, follow the links I posted | 23:58 |
| freem | debian's official documentation says they put dbgsym packages in a different repo | 23:59 |
| rrq | have you tried downloading any -dgbsym package? | 23:59 |
| gnarface | i see a lot of them in the regular devuan repos | 23:59 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!