[gentoo-user] HOWTO: Freezing/unfreezing (groups of) processes
Thanks for all the help over the years fellow Gentoo'ers. Maybe I can
return the favour. So you've got a bunch of programs like Gnumeric or
QEMU or Pale Moon ( or Firefox or Chrome or Opera ) sessions open, that
are chewing up cpu and ram. You need those resouces for another
program, but you don't want to shut those programs down and lose your
place. If the programs could be frozen, cpu usage would go away, and
memory could be swapped out. Here's a real-life example subset of a
"ps -ef" output on my system. Replace "palemoon" with "firefox" or
"chrome" or whatever browser you're using.
waltdnes 4025 3173 0 Jan20 ?01:54:21
/home/waltdnes/pm/palemoon/palemoon -new-instance -p palemoon
waltdnes 7580 3173 4 Jan21 ?17:45:11
/home/waltdnes/pm/palemoon/palemoon -new-instance -p dslr
waltdnes 9813 3173 4 Jan21 ?16:24:23
/home/waltdnes/pm/palemoon/palemoon -new-instance -p wxforum
waltdnes 22455 3173 58 01:31 ?00:08:29
/home/waltdnes/pm/palemoon/palemoon -new-instance -p slashdot
waltdnes 22523 3173 0 01:31 ?00:00:05
/home/waltdnes/pm/palemoon/palemoon -new-instance -p youtube
waltdnes 22660 3173 12 01:45 ?00:00:04 /usr/bin/gnumeric
/home/waltdnes/worldtemps/temperatures/temperatures.gnumeric
waltdnes 20346 20345 4 Jan28 ?08:10:50 /usr/bin/qemu-system-x86_64
-enable-kvm -runas waltdnes -cpu host -monitor vc -display gtk -drive
file=arcac.img,format=raw -netdev user,id=mynetwork -device
e1000,netdev=mynetwork -rtc base=localtime,clock=host -m 1024 -name ArcaOS VM
-vga std -parallel none
You might want to RTFM on the "kill" command if you're skeptical. It
does a lot more than kill programs. "kill -L" will give you a nicely
formatted list of available signals. For this discussion we're
interested in just "SIGCONT" and "SIGSTOP" ( *NOT* "SIGSTP" ). If I
want to freeze the Slashdot session, I can run "kill -SIGSTOP 22455". To
unfreeze it, I can run "kill -SIGCONT 22455". You can "SIGSTOP" on a
pid multiple times consecutively without problems; ditto for "SIGCONT".
So far, so good, but running "ps -ef | grep whatever" and then
typing the kill -SIGSTOP/SIGCONT command on the correct pid is grunt
work, subject to typos. I've set up a couple of scripts in ~/bin to
stop/continue processes, or groups thereof. The following scripts do a
"dumb grep" of "ps -ef" output, redirecting to /dev/shm/temp.txt. That
file is then read, and the second element of each line is the pid, which
is fed to the "kill" command. I store the scripts as ~/bin/pstop and
~/bin/pcont.
== pstop (process stop) script ==
#!/bin/bash
ps -ef | grep ${1} | grep -v "grep ${1}" | grep -v pstop > /dev/shm/temp.txt
while read
do
inputarray=(${REPLY})
kill -SIGSTOP ${inputarray[1]}
done < /dev/shm/temp.txt
pcont (process continue) script
#!/bin/bash
ps -ef | grep ${1} | grep -v "grep ${1}" | grep -v pcont > /dev/shm/temp.txt
while read
do
inputarray=(${REPLY})
kill -SIGCONT ${inputarray[1]}
done < /dev/shm/temp.txt
=
To stop all Pale Moon instances, execute "pstop palemoon". To stop
only the Slashdot session, run "pstop slashdot". Ditto for the pcont
command. I hope people find this useful.
--
Walter Dnes
I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Re: Gentoo as NAS
On Fri, 2021-02-05 at 01:06 +, Grant Edwards wrote: > > The plex-server ebuild appears to require systemd, but it isn't listed > > as a dependency. Am I missing something? > > > Apparently so. The presence of the command systemd_newunit in the .ebuild > > doesn't mean that systemd is required. I am using plex-media-server from this overlay without systemd. It is not required.
Re: [gentoo-user] Re: Gentoo as NAS
I use Plex via Docker and it works great. Super simple to setup a docker-compose file to bring it up (or even a simple script to 'docker run...'). Data stored on a zpool made up of a pair of 3-drive vdevs. More complex than random FreeNAS/Unraid/Whatever setup, but if you're comfortable enough to use Gentoo, I don't think figuring out ZFS and Docker is much of a stretch. On Thu, Feb 4, 2021 at 5:07 PM Grant Edwards wrote: > On 2021-02-05, Grant Edwards wrote: > > On 2021-02-05, Michael Jones wrote: > > > >> Use the plex overlay. > >> > >> It's updated regularly. Faster than the official gentoo repo was. > > > > This one? > > > > https://github.com/comio/plex-overlay/ > > > > The plex-server ebuild appears to require systemd, but it isn't listed > > as a dependency. Am I missing something? > > Apparently so. The presence of the command systemd_newunit in the .ebuild > doesn't mean that systemd is required. > > >
Re: [gentoo-user] spam - different IP's
On Thu, Feb 4, 2021 at 6:07 PM Adam Carter wrote: > On Thursday, February 4, 2021, wrote: > >> I'm perplex with this entry in apache log. >> I'm sure it was done by same person as the timing is very sequential and >> same file-name request, but how they were able to lunch an attack from a >> different IP's different geographical locations. >> Can they spoof an IP? >> >> > Probably just different instances of the same bot scanning for > vulnerabilities. I imagine you will keep seeing that log from many > different ips > FWIW i'm seeing the same traffic. Here's some numbers; $ zgrep -ic wlwmanifest.xml access.log* access.log:16 access.log-20210110.gz:0 access.log-20210117.gz:0 access.log-20210124.gz:34 access.log-20210131.gz:0
[gentoo-user] Re: Gentoo as NAS
On 2021-02-05, Grant Edwards wrote: > On 2021-02-05, Michael Jones wrote: > >> Use the plex overlay. >> >> It's updated regularly. Faster than the official gentoo repo was. > > This one? > > https://github.com/comio/plex-overlay/ > > The plex-server ebuild appears to require systemd, but it isn't listed > as a dependency. Am I missing something? Apparently so. The presence of the command systemd_newunit in the .ebuild doesn't mean that systemd is required.
[gentoo-user] Re: Gentoo as NAS
On 2021-02-05, Michael Jones wrote: > Use the plex overlay. > > It's updated regularly. Faster than the official gentoo repo was. This one? https://github.com/comio/plex-overlay/ The plex-server ebuild appears to require systemd, but it isn't listed as a dependency. Am I missing something? -- Grant
Re: [gentoo-user] Re: Gentoo as NAS
Use the plex overlay. It's updated regularly. Faster than the official gentoo repo was. On Thu, Feb 4, 2021 at 5:56 PM Grant Edwards wrote: > On 2021-02-04, Neil Bothwick wrote: > > On Thu, 4 Feb 2021 15:04:14 -0300, Raphael MD wrote: > > > >> Said that, what could be the effort to turn my Gentoo in a NAS service, > >> setting up SAMBA, Plex, quotas and ZFS? > > > > I see Plex as the main problem, as it is no longer in portage. > > One way round that would be to run it under Docker. > > The whole Plex thing is something I need to figure out. I suppose it's > either give up on it completely or Docker. Complaints in the Plex > forums about it using an obsolte version of Python are pretty much met > with a response of "shut up and go away". :/ > > -- > Grant > > > >
[gentoo-user] Re: Gentoo as NAS
On 2021-02-04, Neil Bothwick wrote: > On Thu, 4 Feb 2021 15:04:14 -0300, Raphael MD wrote: > >> Said that, what could be the effort to turn my Gentoo in a NAS service, >> setting up SAMBA, Plex, quotas and ZFS? > > I see Plex as the main problem, as it is no longer in portage. > One way round that would be to run it under Docker. The whole Plex thing is something I need to figure out. I suppose it's either give up on it completely or Docker. Complaints in the Plex forums about it using an obsolte version of Python are pretty much met with a response of "shut up and go away". :/ -- Grant
Re: [gentoo-user] reflexive dependencies?
On 2/4/21 10:45 PM, Dale wrote: n952162 wrote: On 2/4/21 9:05 PM, Stefano Crocco wrote: On giovedì 4 febbraio 2021 20:49:37 CET n952162 wrote: Is this ok? It's stopped my update in its tracks: $ equery d dev-ruby/*bundler* * These packages depend on dev-ruby/bundler: ... dev-ruby/*rdoc*-6.1.2 (test ? dev-ruby/bundler[ruby_targets_ruby25(-)]) (test ? dev-ruby/bundler[ruby_targets_ruby26(-)]) $ equery d dev-ruby/rdoc * These packages depend on dev-ruby/rdoc: ... dev-ruby/*bundler*-2.1.4 (doc ? dev-ruby/rdoc[ruby_targets_ruby25(-)]) (doc ? dev-ruby/rdoc[ruby_targets_ruby26(-)]) (doc ? dev-ruby/rdoc[ruby_targets_ruby27(-)]) bundler is dependent on rdoc and rdoc is dependent on bundler: /var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment: line 663: rdoc: command not found Emerging rdoc fails because it tries to emerge bundler... Do you have the doc USE flag enabled for bundler? If I understand correctly, bundler only depends on rdoc if that flag is enabled. I think that if you remove the flag, it should work correctly. Stefano No, I have no USE flags for ruby, rdoc, or bundler, unfortunately. I tried this /etc/portage/package.use/, but it didn't help: dev-ruby/bundler -rdoc I read that as the "doc" USE flag not rdoc. May make a difference. Dale :-) :-) Ah, yes, you're right (and confirmed that that approach to preemptive USE-defeating may be effective). But Matt Connell solved the problem with the "eselect ruby" solution.
Re: [gentoo-user] Gentoo as NAS
On Thu, 4 Feb 2021 15:04:14 -0300, Raphael MD wrote: > Said that, what could be the effort to turn my Gentoo in a NAS service, > setting up SAMBA, Plex, quotas and ZFS? I see Plex as the main problem, as it is no longer in portage. One way round that would be to run it under Docker. -- Neil Bothwick In possession of a mind not merely twisted, but actually sprained. pgpAa7raFrBaS.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Gentoo as NAS
I do this with btrfs instead of zfs. Its no more complicated than any other service configuration. Gentoo doesn't make this harder or easier than any other distribution. On Thu, Feb 4, 2021, 12:04 Raphael MD wrote: > Hello everyone, > > I'm thinking about using Gentoo as a NAS serve. I know there are some NAS > distributions like FreeNAS that are claimed to be rock solid, but FreeNAS > support for GPU and other things sounds poor to me. > > Said that, what could be the effort to turn my Gentoo in a NAS service, > setting up SAMBA, Plex, quotas and ZFS? > > Anyone has already tried it? > > Thanks! > > M.S. Raphael Mejias Dias > Nuclear Engineer | Reactors > > Secure e-mail: raphael.mejias.d...@protonmail.com > PGP Key for raph...@gmail.com: > https://pgp.mit.edu/pks/lookup?op=get&search=0x87BC5A746072F951 >
Re: [gentoo-user] reflexive dependencies?
n952162 wrote: > On 2/4/21 9:05 PM, Stefano Crocco wrote: >> On giovedì 4 febbraio 2021 20:49:37 CET n952162 wrote: >>> Is this ok? It's stopped my update in its tracks: >>> >>> $ equery d dev-ruby/*bundler* >>> * These packages depend on dev-ruby/bundler: >>> ... >>> dev-ruby/*rdoc*-6.1.2 (test ? dev-ruby/bundler[ruby_targets_ruby25(-)]) >>> (test ? dev-ruby/bundler[ruby_targets_ruby26(-)]) >>> >>> $ equery d dev-ruby/rdoc >>> * These packages depend on dev-ruby/rdoc: >>> ... >>> dev-ruby/*bundler*-2.1.4 (doc ? dev-ruby/rdoc[ruby_targets_ruby25(-)]) >>> (doc ? dev-ruby/rdoc[ruby_targets_ruby26(-)]) >>> (doc ? dev-ruby/rdoc[ruby_targets_ruby27(-)]) >>> >>> >>> bundler is dependent on rdoc and rdoc is dependent on bundler: >>> >>> /var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment: line 663: >>> rdoc: command not found >>> >>> Emerging rdoc fails because it tries to emerge bundler... >> Do you have the doc USE flag enabled for bundler? If I understand >> correctly, >> bundler only depends on rdoc if that flag is enabled. I think that if >> you >> remove the flag, it should work correctly. >> >> Stefano >> > > No, I have no USE flags for ruby, rdoc, or bundler, unfortunately. > > I tried this /etc/portage/package.use/, but it didn't help: > > dev-ruby/bundler -rdoc > >> > > I read that as the "doc" USE flag not rdoc. May make a difference. Dale :-) :-)
Re: [gentoo-user] virtualbox version mismatch
On 2/4/21 5:58 PM, Jack wrote:
On 2/4/21 11:37 AM, n952162 wrote:
On 2/4/21 5:17 PM, Jack wrote:
On 2/4/21 10:10 AM, n952162 wrote:
On 2/4/21 3:47 PM, Matt Connell (Gmail) wrote:
On Thu, 2021-02-04 at 12:37 +0100, n952162 wrote:
The VirtualBox kernel modules do not match this version of
VirtualBox.
Whenever you update app-emulation/virtualbox *or* your kernel
version,
you need to update app-emulation/virtualbox-modules as well. The
versions of those two packages have to be lock-step, and the latter
needs to be rebuilt whenever your kernel version changes, or else the
previously-built modules will not load.
Both are in my world file:
# grep virtualbox /var/lib/portage/world
app-emulation/virtualbox
app-emulation/virtualbox-modules
If you have already run virtualbox since the last reboot, you might
need to rmmod those modules to unload the older version. Then you can
use modprobe to load the new versions, without having to reboot.
Jack
Good tip, unfortunately, it didn't help:
$ sudo rmmod vboxnetadp vboxnetflt vboxdrv
Password:
$ lsmod | grep vbox
$ startvm txm1.4-new
WARNING: The vboxdrv kernel module is not loaded. Either there is no
module
available for the current kernel (4.19.86-gentoo-x86_64) or it
failed to
load. Please recompile the kernel module and install it by
for m in vbox{drv,netadp,netflt}; do modprobe $m; done
You will not be able to start VMs until this problem is fixed.
Waiting for VM "txm1.4-new" to power on...
VBoxManage: error: The virtual machine 'txm1.4-new' has terminated
unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
component MachineWrap, interface IMachine
That takes away my confidence that it would work after a re-boot ...
You did an rmmod, but I don't see that you loaded the new modules -
the modprobe part. It is possible that they do not get loaded
automatically on demand, but only at boot time, so a manual load
should work.
Yeah, I confess, I saw the rmmod and that light the bulb and I rushed of
to try that ... without really thinking about the second half ... I
somehow had this impression they'd be demand loaded.
Re: [gentoo-user] reflexive dependencies?
On 2/4/21 9:24 PM, Matt Connell (Gmail) wrote: On Thu, 2021-02-04 at 20:49 +0100, n952162 wrote: Is this ok? It's stopped my update in its tracks: /var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment: line 663: rdoc: command not found Emerging rdoc fails because it tries to emerge bundler... I encountered this as well. I needed to use "eselect ruby" to pick a new ruby profile. Once I selected 2.6 (with Rubygems), I was able to finish the emerge process. That did the trick. Thank you.
Re: [gentoo-user] reflexive dependencies?
On Thu, 2021-02-04 at 14:24 -0600, Matt Connell (Gmail) wrote: > Once I selected 2.6 (with Rubygems) To clarify: this should read "ruby26 (with Rubygems)
Re: [gentoo-user] reflexive dependencies?
On Thu, 2021-02-04 at 20:49 +0100, n952162 wrote: > Is this ok? It's stopped my update in its tracks: > > /var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment: line 663: > rdoc: command not found > > Emerging rdoc fails because it tries to emerge bundler... > I encountered this as well. I needed to use "eselect ruby" to pick a new ruby profile. Once I selected 2.6 (with Rubygems), I was able to finish the emerge process.
Re: [gentoo-user] reflexive dependencies?
On 2/4/21 9:05 PM, Stefano Crocco wrote: On giovedì 4 febbraio 2021 20:49:37 CET n952162 wrote: Is this ok? It's stopped my update in its tracks: $ equery d dev-ruby/*bundler* * These packages depend on dev-ruby/bundler: ... dev-ruby/*rdoc*-6.1.2 (test ? dev-ruby/bundler[ruby_targets_ruby25(-)]) (test ? dev-ruby/bundler[ruby_targets_ruby26(-)]) $ equery d dev-ruby/rdoc * These packages depend on dev-ruby/rdoc: ... dev-ruby/*bundler*-2.1.4 (doc ? dev-ruby/rdoc[ruby_targets_ruby25(-)]) (doc ? dev-ruby/rdoc[ruby_targets_ruby26(-)]) (doc ? dev-ruby/rdoc[ruby_targets_ruby27(-)]) bundler is dependent on rdoc and rdoc is dependent on bundler: /var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment: line 663: rdoc: command not found Emerging rdoc fails because it tries to emerge bundler... Do you have the doc USE flag enabled for bundler? If I understand correctly, bundler only depends on rdoc if that flag is enabled. I think that if you remove the flag, it should work correctly. Stefano No, I have no USE flags for ruby, rdoc, or bundler, unfortunately. I tried this /etc/portage/package.use/, but it didn't help: dev-ruby/bundler -rdoc
Re: [gentoo-user] reflexive dependencies?
On giovedì 4 febbraio 2021 20:49:37 CET n952162 wrote: > Is this ok? It's stopped my update in its tracks: > > $ equery d dev-ruby/*bundler* > * These packages depend on dev-ruby/bundler: > ... > dev-ruby/*rdoc*-6.1.2 (test ? dev-ruby/bundler[ruby_targets_ruby25(-)]) > (test ? dev-ruby/bundler[ruby_targets_ruby26(-)]) > > $ equery d dev-ruby/rdoc > * These packages depend on dev-ruby/rdoc: > ... > dev-ruby/*bundler*-2.1.4 (doc ? dev-ruby/rdoc[ruby_targets_ruby25(-)]) > (doc ? dev-ruby/rdoc[ruby_targets_ruby26(-)]) > (doc ? dev-ruby/rdoc[ruby_targets_ruby27(-)]) > > > bundler is dependent on rdoc and rdoc is dependent on bundler: > > /var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment: line 663: > rdoc: command not found > > Emerging rdoc fails because it tries to emerge bundler... Do you have the doc USE flag enabled for bundler? If I understand correctly, bundler only depends on rdoc if that flag is enabled. I think that if you remove the flag, it should work correctly. Stefano
[gentoo-user] reflexive dependencies?
Is this ok? It's stopped my update in its tracks: $ equery d dev-ruby/*bundler* * These packages depend on dev-ruby/bundler: ... dev-ruby/*rdoc*-6.1.2 (test ? dev-ruby/bundler[ruby_targets_ruby25(-)]) (test ? dev-ruby/bundler[ruby_targets_ruby26(-)]) $ equery d dev-ruby/rdoc * These packages depend on dev-ruby/rdoc: ... dev-ruby/*bundler*-2.1.4 (doc ? dev-ruby/rdoc[ruby_targets_ruby25(-)]) (doc ? dev-ruby/rdoc[ruby_targets_ruby26(-)]) (doc ? dev-ruby/rdoc[ruby_targets_ruby27(-)]) bundler is dependent on rdoc and rdoc is dependent on bundler: /var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment: line 663: rdoc: command not found Emerging rdoc fails because it tries to emerge bundler...
Re: [gentoo-user] news 2021-01-30-display-manager-init -- blocked package
On Thu, Feb 4, 2021 at 1:53 PM antlists wrote: > > On 31/01/2021 19:20, Rich Freeman wrote: > > On Sat, Jan 30, 2021 at 11:01 PM Kusoneko wrote: > >> > >> It states that starting the next xorg-server version, ... > >> > >> ... Doing the required update is currently impossible. > >> > >> I am definitely not gonna remember about this > >> in a week or 2 so I'd like to deal with whatever > >> this issue is asap. Is there any way to do this? > > > > You hit on the issue. You can either wait and not have to mess with > > much, or you can force things using keywords as Jacques suggested, and > > then if you want to go back to stable do more work later to transition > > back. > > > Is there a way to say "install this version from ~ if it's more recent > than stable"? That way, as stable catches up and overtakes ~, it reverts > back to stable without any further intervention? When I'm in this sort of situation I tend to stick range atoms in package.accept_keywords. For example, if foo-1.2.3 is stable, and foo-1.3.1 is unstable and I need it for a while, I'll stick this in package.accept_keywords:
Re: [gentoo-user] news 2021-01-30-display-manager-init -- blocked package
On 31/01/2021 19:20, Rich Freeman wrote: On Sat, Jan 30, 2021 at 11:01 PM Kusoneko wrote: It states that starting the next xorg-server version, ... ... Doing the required update is currently impossible. I am definitely not gonna remember about this in a week or 2 so I'd like to deal with whatever this issue is asap. Is there any way to do this? You hit on the issue. You can either wait and not have to mess with much, or you can force things using keywords as Jacques suggested, and then if you want to go back to stable do more work later to transition back. Is there a way to say "install this version from ~ if it's more recent than stable"? That way, as stable catches up and overtakes ~, it reverts back to stable without any further intervention? Cheers, Wol
Re: [gentoo-user] State of emergency is now in effect.
On 30/01/2021 10:48, Michael wrote: Did you try removing the java USE flag from app-office/libreoffice as emerge suggests above to see if it proceeds? Alternatively, you could unmerge dev-java/openjdk and see what portage wants to bring in. Using '--depclean -p -v' on dev-java/openjdk before you unmerge it will show you what else could break. Within LibreOffice, are you using Base? Because if you're not using the database, you shouldn't be using java. Cheers, Wol
Re: [gentoo-user] virtualbox version mismatch
On Thursday, 4 February 2021 11:42:08 GMT Michael wrote: > You may need to modprobe the relevant modules if the above won't also load > them - can't recall if it does. I believe it only recompiles and installs them. -- Regards, Peter.
[gentoo-user] Gentoo as NAS
Hello everyone, I'm thinking about using Gentoo as a NAS serve. I know there are some NAS distributions like FreeNAS that are claimed to be rock solid, but FreeNAS support for GPU and other things sounds poor to me. Said that, what could be the effort to turn my Gentoo in a NAS service, setting up SAMBA, Plex, quotas and ZFS? Anyone has already tried it? Thanks! M.S. Raphael Mejias Dias Nuclear Engineer | Reactors Secure e-mail: raphael.mejias.d...@protonmail.com PGP Key for raph...@gmail.com: https://pgp.mit.edu/pks/lookup?op=get&search=0x87BC5A746072F951
Re: [gentoo-user] virtualbox version mismatch [ RESOLVED ]
On 2/4/21 6:36 PM, Michael wrote: On Thursday, 4 February 2021 17:25:35 GMT n952162 wrote: Sorry, if I gave the impression, when I said: /I tried that (using "module-rebuild")/ that I ran it without the "@". I was just referring to the original suggestion had "@module*s*-rebuild". Oops! My apologies - I was running from apparently faulty memory! :-) Did you run on the host, after you updated your VBox: emerge -uaDv @modules-rebuild In fact, it had emerged successfully: ... [ebuild U ] sys-libs/timezone-data-2020e::gentoo [2020d::gentoo] USE="nls -leaps-timezone -zic-slim" 659 KiB [ebuild U ] app-eselect/eselect-pinentry-0.7.1::gentoo [0.7::gentoo] 0 KiB [ebuild U ] virtual/perl-Data-Dumper-2.174.0-r2::gentoo [2.174.0-r1::gentoo] 0 KiB [ebuild NS] sys-kernel/gentoo-sources-5.4.92:5.4.92::gentoo [4.19.86:4.19.86::gentoo, 5.4.38:5.4.38::gentoo, 5.4.66:5.4.66::gentoo, 5.4.80-r1:5.4.80-r1::gentoo] USE="-build -experimental -symlink" 2938 KiB Total: 4 packages (3 upgrades, 1 in new slot), Size of downloads: 3596 KiB ... but failed to run. I assume you have already installed 'app-emulation/virtualbox-modules' at least once, if VBox was working OK until recently? Otherwise, emerge the package 'app-emulation/virtualbox-modules' and modprobe each module keeping an eye in dmesg to make sure they load without further errors. I followed this advice, to load each module (from equery files virtualbox-modules) by hand, and that worked, for whatever reason that it didn't work before after unloading the modules by hand, as recommended by Jack ... they were not loaded when I just loaded them now ... ah - naturally, I loaded them with sudo, but didn't use sudo when I ran startvm ... Hmmm. We'll see how it starts up tomorrow ;-) OK, as long as the VBox modules were rebuilt after the new kernel symlink was set under /usr/src/linux they should (re)load after a reboot. Loading modules manually requires you run modprobe as root. However, you do not need to start VBox as root, arguably you shouldn't. Just make sure your user is a member of group "vboxusers": # gpasswd -a vboxusers Logout/in as the named user before you can run VBox again. More info you should need it can be found here: https://wiki.gentoo.org/wiki/VirtualBox Well, what's not exactly clear to me is whether the vbox modules are preloaded at boot (i.e. as root) ... it must be that, because vboxmanage doesn't run setuid: $ ls -lL $(type -p vboxmanage) -rwxr-x--- 1 root vboxusers 3570 Feb 3 02:50 /usr/bin/vboxmanage So that was a mistaken assumption I'd had, that the modules would be loaded on demand. Too bad, actually.
Re: [gentoo-user] virtualbox version mismatch [ RESOLVED ]
On Thursday, 4 February 2021 17:25:35 GMT n952162 wrote: > Sorry, if I gave the impression, when I said: > > /I tried that (using "module-rebuild")/ > > that I ran it without the "@". I was just referring to the original > suggestion had "@module*s*-rebuild". Oops! My apologies - I was running from apparently faulty memory! :-) > Did you run on the host, after you updated your VBox: > > emerge -uaDv @modules-rebuild > > In fact, it had emerged successfully: > > ... > [ebuild U ] sys-libs/timezone-data-2020e::gentoo > [2020d::gentoo] USE="nls -leaps-timezone -zic-slim" 659 KiB > [ebuild U ] app-eselect/eselect-pinentry-0.7.1::gentoo > [0.7::gentoo] 0 KiB > [ebuild U ] virtual/perl-Data-Dumper-2.174.0-r2::gentoo > [2.174.0-r1::gentoo] 0 KiB > [ebuild NS] sys-kernel/gentoo-sources-5.4.92:5.4.92::gentoo > [4.19.86:4.19.86::gentoo, 5.4.38:5.4.38::gentoo, > 5.4.66:5.4.66::gentoo, 5.4.80-r1:5.4.80-r1::gentoo] USE="-build > -experimental -symlink" 2938 KiB > > Total: 4 packages (3 upgrades, 1 in new slot), Size of downloads: > 3596 KiB > ... > > but failed to run. > > > I assume you have already installed 'app-emulation/virtualbox-modules' at > > least once, if VBox was working OK until recently? Otherwise, emerge the > > package 'app-emulation/virtualbox-modules' and modprobe each module > > keeping an eye in dmesg to make sure they load without further errors. > > I followed this advice, to load each module (from equery files > virtualbox-modules) by hand, and that worked, for whatever reason that > it didn't work before after unloading the modules by hand, as > recommended by Jack ... they were not loaded when I just loaded them now > ... ah - naturally, I loaded them with sudo, but didn't use sudo when I > ran startvm ... Hmmm. We'll see how it starts up tomorrow ;-) OK, as long as the VBox modules were rebuilt after the new kernel symlink was set under /usr/src/linux they should (re)load after a reboot. Loading modules manually requires you run modprobe as root. However, you do not need to start VBox as root, arguably you shouldn't. Just make sure your user is a member of group "vboxusers": # gpasswd -a vboxusers Logout/in as the named user before you can run VBox again. More info you should need it can be found here: https://wiki.gentoo.org/wiki/VirtualBox signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] virtualbox version mismatch [ RESOLVED ]
On 2/4/21 5:56 PM, Michael wrote:
On Thursday, 4 February 2021 16:37:01 GMT n952162 wrote:
On 2/4/21 5:17 PM, Jack wrote:
On 2/4/21 10:10 AM, n952162 wrote:
On 2/4/21 3:47 PM, Matt Connell (Gmail) wrote:
On Thu, 2021-02-04 at 12:37 +0100, n952162 wrote:
The VirtualBox kernel modules do not match this version of VirtualBox.
Whenever you update app-emulation/virtualbox *or* your kernel version,
you need to update app-emulation/virtualbox-modules as well. The
versions of those two packages have to be lock-step, and the latter
needs to be rebuilt whenever your kernel version changes, or else the
previously-built modules will not load.
Both are in my world file:
# grep virtualbox /var/lib/portage/world
app-emulation/virtualbox
app-emulation/virtualbox-modules
If you have already run virtualbox since the last reboot, you might
need to rmmod those modules to unload the older version. Then you can
use modprobe to load the new versions, without having to reboot.
Jack
Good tip, unfortunately, it didn't help:
$ sudo rmmod vboxnetadp vboxnetflt vboxdrv
Password:
$ lsmod | grep vbox
$ startvm txm1.4-new
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.19.86-gentoo-x86_64) or it
failed to
load. Please recompile the kernel module and install it by
for m in vbox{drv,netadp,netflt}; do modprobe $m; done
You will not be able to start VMs until this problem is fixed.
Waiting for VM "txm1.4-new" to power on...
VBoxManage: error: The virtual machine 'txm1.4-new' has terminated
unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
component MachineWrap, interface IMachine
That takes away my confidence that it would work after a re-boot ...
Try again updating the modules, but use the correct syntax. The prefix "@"
denotes this is a predefined set and it will rebuild any packages which own
files in your /lib/modules:
emerge -1aDv @module-rebuild
???
Sorry, if I gave the impression, when I said:
/I tried that (using "module-rebuild")/
that I ran it without the "@". I was just referring to the original
suggestion had "@module*s*-rebuild".
Did you run on the host, after you updated your VBox:
emerge -uaDv @modules-rebuild
In fact, it had emerged successfully:
...
[ebuild U ] sys-libs/timezone-data-2020e::gentoo
[2020d::gentoo] USE="nls -leaps-timezone -zic-slim" 659 KiB
[ebuild U ] app-eselect/eselect-pinentry-0.7.1::gentoo
[0.7::gentoo] 0 KiB
[ebuild U ] virtual/perl-Data-Dumper-2.174.0-r2::gentoo
[2.174.0-r1::gentoo] 0 KiB
[ebuild NS ] sys-kernel/gentoo-sources-5.4.92:5.4.92::gentoo
[4.19.86:4.19.86::gentoo, 5.4.38:5.4.38::gentoo,
5.4.66:5.4.66::gentoo, 5.4.80-r1:5.4.80-r1::gentoo] USE="-build
-experimental -symlink" 2938 KiB
Total: 4 packages (3 upgrades, 1 in new slot), Size of downloads:
3596 KiB
...
but failed to run.
I assume you have already installed 'app-emulation/virtualbox-modules' at
least once, if VBox was working OK until recently? Otherwise, emerge the
package 'app-emulation/virtualbox-modules' and modprobe each module keeping an
eye in dmesg to make sure they load without further errors.
I followed this advice, to load each module (from equery files
virtualbox-modules) by hand, and that worked, for whatever reason that
it didn't work before after unloading the modules by hand, as
recommended by Jack ... they were not loaded when I just loaded them now
... ah - naturally, I loaded them with sudo, but didn't use sudo when I
ran startvm ... Hmmm. We'll see how it starts up tomorrow ;-)
Re: [gentoo-user] virtualbox version mismatch
On 2/4/21 11:37 AM, n952162 wrote:
On 2/4/21 5:17 PM, Jack wrote:
On 2/4/21 10:10 AM, n952162 wrote:
On 2/4/21 3:47 PM, Matt Connell (Gmail) wrote:
On Thu, 2021-02-04 at 12:37 +0100, n952162 wrote:
The VirtualBox kernel modules do not match this version of
VirtualBox.
Whenever you update app-emulation/virtualbox *or* your kernel version,
you need to update app-emulation/virtualbox-modules as well. The
versions of those two packages have to be lock-step, and the latter
needs to be rebuilt whenever your kernel version changes, or else the
previously-built modules will not load.
Both are in my world file:
# grep virtualbox /var/lib/portage/world
app-emulation/virtualbox
app-emulation/virtualbox-modules
If you have already run virtualbox since the last reboot, you might
need to rmmod those modules to unload the older version. Then you can
use modprobe to load the new versions, without having to reboot.
Jack
Good tip, unfortunately, it didn't help:
$ sudo rmmod vboxnetadp vboxnetflt vboxdrv
Password:
$ lsmod | grep vbox
$ startvm txm1.4-new
WARNING: The vboxdrv kernel module is not loaded. Either there is no
module
available for the current kernel (4.19.86-gentoo-x86_64) or it
failed to
load. Please recompile the kernel module and install it by
for m in vbox{drv,netadp,netflt}; do modprobe $m; done
You will not be able to start VMs until this problem is fixed.
Waiting for VM "txm1.4-new" to power on...
VBoxManage: error: The virtual machine 'txm1.4-new' has terminated
unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
component MachineWrap, interface IMachine
That takes away my confidence that it would work after a re-boot ...
You did an rmmod, but I don't see that you loaded the new modules - the
modprobe part. It is possible that they do not get loaded automatically
on demand, but only at boot time, so a manual load should work.
Re: [gentoo-user] virtualbox version mismatch
On Thu, 4 Feb 2021 17:37:01 +0100, n952162 wrote:
> WARNING: The vboxdrv kernel module is not loaded. Either there is no
> module available for the current kernel (4.19.86-gentoo-x86_64) or it
> failed to
> load. Please recompile the kernel module and install it by
>
> for m in vbox{drv,netadp,netflt}; do modprobe $m; done
Did you do this?
Presence in your world file is not relevant and you are not changing
versions so -u won't pick them up.
--
Neil Bothwick
"Energize!" said Picard and the pink bunny appeared...
pgpqIegM7LvEf.pgp
Description: OpenPGP digital signature
Re: [gentoo-user] virtualbox version mismatch
On Thursday, 4 February 2021 16:37:01 GMT n952162 wrote:
> On 2/4/21 5:17 PM, Jack wrote:
> > On 2/4/21 10:10 AM, n952162 wrote:
> >> On 2/4/21 3:47 PM, Matt Connell (Gmail) wrote:
> >>> On Thu, 2021-02-04 at 12:37 +0100, n952162 wrote:
> The VirtualBox kernel modules do not match this version of VirtualBox.
> >>>
> >>> Whenever you update app-emulation/virtualbox *or* your kernel version,
> >>> you need to update app-emulation/virtualbox-modules as well. The
> >>> versions of those two packages have to be lock-step, and the latter
> >>> needs to be rebuilt whenever your kernel version changes, or else the
> >>> previously-built modules will not load.
> >>
> >> Both are in my world file:
> >>
> >> # grep virtualbox /var/lib/portage/world
> >> app-emulation/virtualbox
> >> app-emulation/virtualbox-modules
> >
> > If you have already run virtualbox since the last reboot, you might
> > need to rmmod those modules to unload the older version. Then you can
> > use modprobe to load the new versions, without having to reboot.
> >
> > Jack
>
> Good tip, unfortunately, it didn't help:
>
> $ sudo rmmod vboxnetadp vboxnetflt vboxdrv
> Password:
> $ lsmod | grep vbox
> $ startvm txm1.4-new
> WARNING: The vboxdrv kernel module is not loaded. Either there is no module
> available for the current kernel (4.19.86-gentoo-x86_64) or it
> failed to
> load. Please recompile the kernel module and install it by
>
> for m in vbox{drv,netadp,netflt}; do modprobe $m; done
>
> You will not be able to start VMs until this problem is fixed.
> Waiting for VM "txm1.4-new" to power on...
> VBoxManage: error: The virtual machine 'txm1.4-new' has terminated
> unexpectedly during startup with exit code 1 (0x1)
> VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
> component MachineWrap, interface IMachine
>
> That takes away my confidence that it would work after a re-boot ...
Try again updating the modules, but use the correct syntax. The prefix "@"
denotes this is a predefined set and it will rebuild any packages which own
files in your /lib/modules:
emerge -1aDv @module-rebuild
I assume you have already installed 'app-emulation/virtualbox-modules' at
least once, if VBox was working OK until recently? Otherwise, emerge the
package 'app-emulation/virtualbox-modules' and modprobe each module keeping an
eye in dmesg to make sure they load without further errors.
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] virtualbox version mismatch
On 2/4/21 5:17 PM, Jack wrote:
On 2/4/21 10:10 AM, n952162 wrote:
On 2/4/21 3:47 PM, Matt Connell (Gmail) wrote:
On Thu, 2021-02-04 at 12:37 +0100, n952162 wrote:
The VirtualBox kernel modules do not match this version of VirtualBox.
Whenever you update app-emulation/virtualbox *or* your kernel version,
you need to update app-emulation/virtualbox-modules as well. The
versions of those two packages have to be lock-step, and the latter
needs to be rebuilt whenever your kernel version changes, or else the
previously-built modules will not load.
Both are in my world file:
# grep virtualbox /var/lib/portage/world
app-emulation/virtualbox
app-emulation/virtualbox-modules
If you have already run virtualbox since the last reboot, you might
need to rmmod those modules to unload the older version. Then you can
use modprobe to load the new versions, without having to reboot.
Jack
Good tip, unfortunately, it didn't help:
$ sudo rmmod vboxnetadp vboxnetflt vboxdrv
Password:
$ lsmod | grep vbox
$ startvm txm1.4-new
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.19.86-gentoo-x86_64) or it
failed to
load. Please recompile the kernel module and install it by
for m in vbox{drv,netadp,netflt}; do modprobe $m; done
You will not be able to start VMs until this problem is fixed.
Waiting for VM "txm1.4-new" to power on...
VBoxManage: error: The virtual machine 'txm1.4-new' has terminated
unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
component MachineWrap, interface IMachine
That takes away my confidence that it would work after a re-boot ...
Re: [gentoo-user] virtualbox version mismatch
On 2/4/21 10:10 AM, n952162 wrote: On 2/4/21 3:47 PM, Matt Connell (Gmail) wrote: On Thu, 2021-02-04 at 12:37 +0100, n952162 wrote: The VirtualBox kernel modules do not match this version of VirtualBox. Whenever you update app-emulation/virtualbox *or* your kernel version, you need to update app-emulation/virtualbox-modules as well. The versions of those two packages have to be lock-step, and the latter needs to be rebuilt whenever your kernel version changes, or else the previously-built modules will not load. Both are in my world file: # grep virtualbox /var/lib/portage/world app-emulation/virtualbox app-emulation/virtualbox-modules If you have already run virtualbox since the last reboot, you might need to rmmod those modules to unload the older version. Then you can use modprobe to load the new versions, without having to reboot. Jack
Re: [gentoo-user] virtualbox version mismatch
On 2/4/21 3:47 PM, Matt Connell (Gmail) wrote: On Thu, 2021-02-04 at 12:37 +0100, n952162 wrote: The VirtualBox kernel modules do not match this version of VirtualBox. Whenever you update app-emulation/virtualbox *or* your kernel version, you need to update app-emulation/virtualbox-modules as well. The versions of those two packages have to be lock-step, and the latter needs to be rebuilt whenever your kernel version changes, or else the previously-built modules will not load. Both are in my world file: # grep virtualbox /var/lib/portage/world app-emulation/virtualbox app-emulation/virtualbox-modules
Re: [gentoo-user] virtualbox version mismatch
On 2/4/21 12:42 PM, Michael wrote: On Thursday, 4 February 2021 11:37:59 GMT n952162 wrote: After updating, when I try to start my virtual machine (to update it), I get this: RTR3InitEx failed with rc=-1912 (rc=-1912) The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/sbin/vboxconfig' may correct this. Make sure that you are not mixing builds of VirtualBox from different sources. where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user. Has anybody run into this and found a solution? There's no /sbin/vboxconfig, btw. Did you run on the host, after you updated your VBox: emerge -uaDv @modules-rebuild You may need to modprobe the relevant modules if the above won't also load them - can't recall if it does. Thank you. I tried that (using "module-rebuild") and it didn't make a change, immediately. Perhaps I need to reboot to get the change? I've got too many things going on my desktop now, but I'll try that later today.
Re: [gentoo-user] virtualbox version mismatch
On Thu, 2021-02-04 at 12:37 +0100, n952162 wrote: > The VirtualBox kernel modules do not match this version of VirtualBox. Whenever you update app-emulation/virtualbox *or* your kernel version, you need to update app-emulation/virtualbox-modules as well. The versions of those two packages have to be lock-step, and the latter needs to be rebuilt whenever your kernel version changes, or else the previously-built modules will not load.
Re: [gentoo-user] virtualbox version mismatch
On Thursday, 4 February 2021 11:37:59 GMT n952162 wrote: > After updating, when I try to start my virtual machine (to update it), I > get this: > > RTR3InitEx failed with rc=-1912 (rc=-1912) The VirtualBox kernel > modules do not match this version of VirtualBox. The installation of > VirtualBox was apparently not successful. Executing > '/sbin/vboxconfig' may correct this. Make sure that you are not > mixing builds of VirtualBox from different sources. where: > supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH > (-1912) - The installed support driver doesn't match the version of > the user. > > Has anybody run into this and found a solution? There's no > /sbin/vboxconfig, btw. Did you run on the host, after you updated your VBox: emerge -uaDv @modules-rebuild You may need to modprobe the relevant modules if the above won't also load them - can't recall if it does. signature.asc Description: This is a digitally signed message part.
[gentoo-user] virtualbox version mismatch
After updating, when I try to start my virtual machine (to update it), I get this: RTR3InitEx failed with rc=-1912 (rc=-1912) The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/sbin/vboxconfig' may correct this. Make sure that you are not mixing builds of VirtualBox from different sources. where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user. Has anybody run into this and found a solution? There's no /sbin/vboxconfig, btw.
Re: [gentoo-user] spam - different IP's
在 2021/2/4 下午1:22, the...@sys-concept.com 写道: I'm perplex with this entry in apache log. I'm sure it was done by same person as the timing is very sequential and same file-name request, but how they were able to lunch an attack from a different IP's different geographical locations. Can they spoof an IP? This is very common. If someone intentionally attacks, they usually have an IP pool to avoid being blocked. Also ISP sometimes give dynamic IP to users, cause IP changes of normal users. And one suggestion, just put part of an IP to the list, use '*' to replace some fields to avoid information leakage -- bobwxc F645 5C7A 08E8 A637 24C6 D59E 36E9 4EAB B53E 516B OpenPGP_signature Description: OpenPGP digital signature
