Re: [gentoo-user] ssh Connection reset by port 22
On 12/15/2020 11:35 PM, the...@sys-concept.com wrote: [snip] > > tail -f /var/log/auth.log (on the server) > does not show any log-in attempt > > only: > sshd: Server listening on 0.0.0.0 port 22 > sshd: Server listening on :: port 22 Solved by reinstalling openssh.
Re: [gentoo-user] ssh Connection reset by port 22
On 12/15/2020 10:41 PM, cal wrote: > On 12/15/20 9:36 PM, the...@sys-concept.com wrote: >> On 12/15/2020 07:53 PM, the...@sys-concept.com wrote: >>> During compiling -uavDN @world one of the package refuse to compile >>> >>> sys-auth/polkit-0.118::gentoo failed (configure phase): >>> econf failed >> [snip] >>> >>> Now, I can no longer ssh to to it, I get: >>> Connection reset by 10.0.0.100 port 22 >> >> perl-cleaner --reallyall -- -av solved the problem with: >> sys-auth/polkit-0.118 >> but I still get the error when trying to ssh: >> >> Connection reset by 10.0.0.100 port 22 >> > > Is there anything interesting if you run ssh -vvv (you can vary the > amount of 'v's) to increase the verbosity of the ssh client and see what > it's doing prior to the connection reset? > > Have you tried restarting sshd on the server? tail -f /var/log/auth.log (on the server) does not show any log-in attempt only: sshd: Server listening on 0.0.0.0 port 22 sshd: Server listening on :: port 22
Re: [gentoo-user] ssh Connection reset by port 22
On 12/15/2020 10:41 PM, cal wrote: > On 12/15/20 9:36 PM, the...@sys-concept.com wrote: >> On 12/15/2020 07:53 PM, the...@sys-concept.com wrote: >>> During compiling -uavDN @world one of the package refuse to compile >>> >>> sys-auth/polkit-0.118::gentoo failed (configure phase): >>> econf failed >> [snip] >>> >>> Now, I can no longer ssh to to it, I get: >>> Connection reset by 10.0.0.100 port 22 >> >> perl-cleaner --reallyall -- -av solved the problem with: >> sys-auth/polkit-0.118 >> but I still get the error when trying to ssh: >> >> Connection reset by 10.0.0.100 port 22 >> > > Is there anything interesting if you run ssh -vvv (you can vary the > amount of 'v's) to increase the verbosity of the ssh client and see what > it's doing prior to the connection reset? > > Have you tried restarting sshd on the server? > Nothing that would indicate any error. OpenSSH_7.5p1-hpn14v12lpk, OpenSSL 1.0.2n 7 Dec 2017 debug1: Reading configuration data /etc/ssh/ssh_config debug2: resolving "10.0.0.100" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to 10.0.0.100 [10.0.0.100] port 22. debug1: Connection established. debug1: identity file /home/joseph/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /home/joseph/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/joseph/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/joseph/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/joseph/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/joseph/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/joseph/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/joseph/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.5p1-hpn14v12lpk debug1: Remote protocol version 2.0, remote software version OpenSSH_8.1 debug1: match: OpenSSH_8.1 pat OpenSSH* compat 0x0400 debug1: Remote is NON-HPN aware debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to 10.0.0.100:22 as 'joseph' debug3: hostkeys_foreach: reading file "/home/joseph/.ssh/known_hosts" debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent Connection reset by 10.0.0.100 port 22
Re: [gentoo-user] ssh Connection reset by port 22
On 12/15/20 9:36 PM, the...@sys-concept.com wrote: > On 12/15/2020 07:53 PM, the...@sys-concept.com wrote: >> During compiling -uavDN @world one of the package refuse to compile >> >> sys-auth/polkit-0.118::gentoo failed (configure phase): >>econf failed > [snip] >> >> Now, I can no longer ssh to to it, I get: >> Connection reset by 10.0.0.100 port 22 > > perl-cleaner --reallyall -- -av solved the problem with: > sys-auth/polkit-0.118 > but I still get the error when trying to ssh: > > Connection reset by 10.0.0.100 port 22 > Is there anything interesting if you run ssh -vvv (you can vary the amount of 'v's) to increase the verbosity of the ssh client and see what it's doing prior to the connection reset? Have you tried restarting sshd on the server?
Re: [gentoo-user] ssh Connection reset by port 22
On 12/15/2020 07:53 PM, the...@sys-concept.com wrote: > During compiling -uavDN @world one of the package refuse to compile > > sys-auth/polkit-0.118::gentoo failed (configure phase): > econf failed [snip] > > Now, I can no longer ssh to to it, I get: > Connection reset by 10.0.0.100 port 22 perl-cleaner --reallyall -- -av solved the problem with: sys-auth/polkit-0.118 but I still get the error when trying to ssh: Connection reset by 10.0.0.100 port 22
[gentoo-user] syslog-ng: filter plugin NOT not found ????
Help me understand this, please? I have ISC dhcpd configured to log to
syslog.local7 (since I don't see an option to force it into it's own log
file). So I went into my syslog-ng file and created two filters, just
like on the example page of syslog-ng.com:
filter dhcpmsgs { facility(23) );
filter non_dhcp { NOT filter(dhcpmsgs) )
I quoted almost directly from the example page on syslog-ng.com, but I
keep getting this error when I reload syslog-ng's config:
Error parsing filter expression, filter plugin NOT not found OR you may
not used double quotes in your filter expression in
/etc/syslog-ng/syslog-ng.conf:25:18-25:21:
What did I do wrong? Here's the lines I modified from the syslog-ng page:
filter demo_filter { host("example") and match("deny" value("MESSAGE")) };
filter inverted_demo_filter { NOT filter(demo_filter) }
You can see the page at:
https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.16/administration-guide/53
--
Dan Egli
From my Test Server
[gentoo-user] ssh Connection reset by port 22
During compiling -uavDN @world one of the package refuse to compile sys-auth/polkit-0.118::gentoo failed (configure phase): econf failed Call stack: ebuild.sh, line 125: Called src_configure environment, line 2211: Called econf '--localstatedir=/var' '--disable-static' '--enable-man-pages' '--disable-gtk-doc' '--disable-examples' '--enable-libelogind' '--enable-introspection' '--enable-nls' '--with-pam-module-dir=/lib/security' '--with-authfw=pam' '--disable-libsystemd-login' '--with-systemdsystemunitdir=/lib/systemd/system' '--disable-test' '--with-os-type=gentoo' phase-helpers.sh, line 680: Called __helpers_die 'econf failed' isolated-functions.sh, line 112: Called die The specific snippet of code: die "$@" Now, I can no longer ssh to to it, I get: Connection reset by 10.0.0.100 port 22
Re: [gentoo-user] Upgrade an old system
On Mon, Dec 14, 2020 at 02:57:22PM -0700, the...@sys-concept.com wrote: > [snip] > > emerge --update --oneshot portage > > !!! All ebuilds that could satisfy > ">=app-crypt/openpgp-keys-gentoo-release-20180706" have been masked. > !!! One of the following masked packages is required to complete your request: > - app-crypt/openpgp-keys-gentoo-release-20200704::gentoo (masked by: EAPI 7) > > The current version of portage supports EAPI '6'. You must upgrade to a > newer version of portage before EAPI masked packages can be installed. > (dependency required by > "sys-apps/portage-2.3.99-r2::gentoo[rsync-verify,-build]" [ebuild]) > (dependency required by "portage" [argument]) > > I don't even have "app-crypt/openpgp-keys-gentoo-release" installed why is it > complaining? > I've done a similar update recently, it's definitely possible if you know what you're doing. A few things: First, you need to update portage. To do so, you'll need to manually downgrade the portage ebuild from EAPI 7 to EAPI 6 (simply change the number in the ebuild). First, emerge it without rsync-verify. Once you have portage up to date, it'll support EAPI 7 and life'll be easier. You can then reemerge it with rsync-verify, as the EAPI 7 dependencies will be installable this time. Then, I'd recommend upgrading the toolchain (binutils, gcc, glibc), otherwise you might run into compilation issues. After that, you can update packages. For big updates like this, I like to do it by chunks as it's easier (and it makes reading the emerge plan less painful). Like all the perl packages, then all the python packages, and so on. For that, the "emerge by path" feature is convenient; for example to update python packages: emerge -au /usr/lib/python3.7 In case force-unmerging python modules makes the update easier (resolving blocks), you can do so. That's actually safe to do, portage will still be able to emerge packages. Python itself (the interpreter) is the only hard dependency of portage. Hope this helps, and good luck with your update!
Re: [gentoo-user] paraview build
On 2020.12.15 15:36, Valmor F. de Almeida wrote: Hello, Has anyone been able to build sci-visualization/paraview either through portage or outside portage? Currently I can't either way. Thanks for inputs. -- Valmor I just build paraview-5.8.1 using portage/emerge with no problems, other than unmasking it and cgnslib and accepting the license. I'm using gcc 10.2.0-r3, in case it matters. Are you getting any error messages? You aren't likely to get much input without providing more information.
[gentoo-user] paraview build
Hello, Has anyone been able to build sci-visualization/paraview either through portage or outside portage? Currently I can't either way. Thanks for inputs. -- Valmor
Re: [gentoo-user] CPU you selected does not support x86-64 instruction set
On Tuesday, 15 December 2020 07:50:00 GMT J. Roeleveld wrote: > On Tuesday, December 15, 2020 8:08:46 AM CET bobwxc wrote: > > 在 2020/12/15 下午2:59, the...@sys-concept.com 写道: > > > On 12/14/2020 11:50 PM, J. Roeleveld wrote: > > >> On Tuesday, December 15, 2020 7:17:57 AM CET the...@sys-concept.com > > wrote: > > >>> On 12/14/2020 06:21 PM, the...@sys-concept.com wrote: > > By mistake on new installation I untar wrong: stage-3 x86_64 instead > > of > > i686 > > > > during kernel compiling I got: > > cc1: error: CPU you selected does not support x86-64 instruction set > > > > Is it possible to untar new stage-3 (i686) over current one, or I > > need > > to delete all the folders? > > >>> > > >>> After selecting stage-3 (i686) I still get the same error message when > > >>> trying to compile kernel: > > >>> > > >>> CC scripts/mod/empty.o > > >>> cc1: error: CPU you selected does not support x86-64 instruction set > > >>> make[1]: *** [scripts/Makefile.build:266: scripts/mod/empty.o] Error 1 > > >>> make: *** [Makefile:1137: prepare0] Error 2 > > >>> > > >>> The CPU I have: > > >>> AMD FX(tm)-8150 Eight-Core Processor > > >> > > >> Isn't this a 64-bit CPU? > > >> If you boot using a 64bit live-image (the gentoo-admin ISO as an > > >> example), you should be able to actually use 64bit. > > >> > > >> -- > > >> Joost > > > > > > I'm confused as well, setting from make.conf on this CPU with previous > > > kernel was: > > > CHOST="x86_64-pc-linux-gnu" > > > > As Joost says, maybe you can try boot from a 64bit install image to test > > that. > > > > If you can, you may re-install your system to use 64bit. > > > > Only a little chance that your cpu has some problem with x64 module. > > I did a fresh install last weekend and using the 64-bit version from: > https://www.gentoo.org/downloads/ > > actually worked. > > I copied it to a USB-stick using dd: > # dd if=...path...toiso of=/dev/ > > Took a little bit (as USB-stick is old...) > > -- > Joost The CPU is 64-bit and as has already been suggested using a 64-bit LiveCD/USB to boot with and install will work fine. For requisite CFLAGS in /etc/ portage/make.conf, take a look here: https://wiki.gentoo.org/wiki/Safe_CFLAGS signature.asc Description: This is a digitally signed message part.
