Ask a Question related to FreeBSD, Design and Development.
-
Matt Rechkemmer #1
Ack, the mysql41-server port killed my box
Lately my FreeBSD 5.3R system has been running fine. Tonight I decided to
load the mysql 4.1.x port. After loading it, glancing at mysql-server.sh, and
firing it up, things went haywire.
At the time I had two root sessions open, as well as two normal users. My
normal users started getting permission denied for everything, new users are
unable to login receiving this via SSHd:
No supported authentication methods left to try!
Root cannot query any user information. /etc/passwd and /etc/master.passwd
look fine. MySQL.d is NOT running, it never did startup, and now I am
effectively locked out of the system if I logout.
It's obviously authenticated since /var/log/auth.log reports:
Feb 19 04:51:17 hybrid sshd[79901]: Accepted keyboard-interactive/pam for
theuser from 172.17.1.11 port 2101 ssh2
Any help is GREATLY appreciated, Google has so far yieled nothing on this
topic.
Thanks!
Matt Rechkemmer
[email]tiberius@trancell.org[/email]
Matt Rechkemmer Guest
-
Win2000 --> Win2003 server upgrade killed osx newconnects
hopefully I can explain this thoroughly... - We have about 50 Contribute users and 4 Dreamweaver Admins accessing our college website. - Users... -
set Port range in sandbox Server/Ports
Hi I am looking at how to allowed a range of ports in the sandbox security. But somehow I can't get it work. In the sandbox Server/Ports page,... -
Binding server to port < 1024
On Mon, Sep 01, 2003 at 10:30:23PM +0000, Andreas Schwarz wrote: You can't. Only root can bind to ports under 1024 on *nix. The way to do it... -
killed process
I have a SCO 5.0.4 enteprise Since a week , i have to restart two processes a couple of times in the day. I don't know how these processes are... -
Web Server on Port 8080
I have multiple development nodes on my network so each machine has a different port for the web server. On one particular machine I'd like to... -
Emanuel Strobl #2
Re: Ack, the mysql41-server port killed my box
Am Samstag, 19. Februar 2005 12:06 schrieb Matt Rechkemmer:
Just a wild guess, perhaps there is any pam module which tries to authenticate> Lately my FreeBSD 5.3R system has been running fine. Tonight I decided to
> load the mysql 4.1.x port. After loading it, glancing at mysql-server.sh,
> and firing it up, things went haywire.
>
> At the time I had two root sessions open, as well as two normal users. My
> normal users started getting permission denied for everything, new users
> are unable to login receiving this via SSHd:
>
> No supported authentication methods left to try!
against the mysql database?. It sounds like....
-Harry
-----BEGIN PGP SIGNATURE----->
> Root cannot query any user information. /etc/passwd and /etc/master.passwd
> look fine. MySQL.d is NOT running, it never did startup, and now I am
> effectively locked out of the system if I logout.
>
> It's obviously authenticated since /var/log/auth.log reports:
> Feb 19 04:51:17 hybrid sshd[79901]: Accepted keyboard-interactive/pam for
> theuser from 172.17.1.11 port 2101 ssh2
>
> Any help is GREATLY appreciated, Google has so far yieled nothing on this
> topic.
>
> Thanks!
>
> Matt Rechkemmer
> [email]tiberius@trancell.org[/email]
> _______________________________________________
> [email]freebsd-questions@freebsd.org[/email] mailing list
> [url]http://lists.freebsd.org/mailman/listinfo/freebsd-questions[/url]
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe@freebsd.org"
Version: GnuPG v1.4.0 (FreeBSD)
iD8DBQBCGdUzBylq0S4AzzwRAs1mAKCCM4WD/xXniACN1EFY42+gLZufqACfQ3ly
8gVSKIYsVJp/dSfJ3ZncRTo=
=0G7U
-----END PGP SIGNATURE-----
Emanuel Strobl Guest
-
Matt Rechkemmer #3
Re: Ack, the mysql41-server port killed my box
On Mon, Feb 21, 2005 at 01:33:50PM +0100, Emanuel Strobl wrote:
Actually after much effort I figured it out. The mysql41-server port (v>
> Just a wild guess, perhaps there is any pam module which tries to
> authenticate against the mysql database?. It sounds like....
>
> -Harry
4.1.10), set the permissions on /. and /.. to 0700 instead of 0755. Once I
set these back to normal, things on the system returned to normal operation.
Matt Rechkemmer Guest



Reply With Quote

