Re: [gentoo-user] vmware-server requires a serial number, but is free? how does this work
Goto: http://www.vmware.com/download/server/ Right under Download VMware Server (in orange) you will see a link that reads register for your free serial number(s). On Dec 21, 2007 3:33 PM, Kevin O'Gorman [EMAIL PROTECTED] wrote: I've emerged and partly configured vmware-server-1.0.4, but it is asking for a 20-digit serial number to complete the configuration. I understood this to be a free product, as it says on the VMware site. But I didn't notice anything about a serial number. Do I just make it up, or did I miss something on vmware.com? ++ kevin -- Kevin O'Gorman, PhD -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] cdrecord says permission denied
The only things that I can guess are that it is trying to update something in /proc or it needs to load a kernel module before writing. Just for fun - try burning a disk as root. Then try burning another dist as a non-root user. If the the second disk burns then one or the other of the above is the problem. -Good Luck, Stephen On 9/11/07, Renat Golubchyk [EMAIL PROTECTED] wrote: On Tue, 11 Sep 2007 15:04:04 -0300 Rafael Barrera Oro [EMAIL PROTECTED] wrote: did you try adding yourself to the cdrom group? I *am* in the cdrom group, as I have already wrote. $ groups adm wheel cron audio cdrom video cdrw usb users locate portage plugdev Renat -- Probleme kann man niemals mit derselben Denkweise loesen, durch die sie entstanden sind. (Einstein) -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] SSH won't restart
This process is the ssh daemon: root 2988 1 0 Sep04 ?00:00:00 /usr/sbin/sshd Two things: before killing the process with the KILL signal, I would try killing it with TERM kill -TERM 2988 If that doesn't work then kill the process with the KILL signal. I would also use: /etc/init.d/sshd restart This will give the init script a chance to do some cleanup work before restarting -Best of Luck, Stephen On 9/10/07, Grant [EMAIL PROTECTED] wrote: I just upgraded ssh and when I try to restart I get: * Stopping sshd ... [ !! ] I don't see anything about it in '/var/log/sshd/current'. How can I figure out what is wrong? I'm a little nervous because I don't want to shut myself out of this remote server. I had a similar issue after a previous update to ssh when I went to restart it to get it to use the new binaries. One of the nice features of sshd is that your current session will say active even if you kill the sshd daemon process. Of course, if you get disconnected then you will not be able to log back in, so it's good to do what you need to quickly if you do need to kill (or if it's really stuck, kill -9) the process. When I had this problem I issued a `kill -9 PID_NUMBER /etc/init.d/sshd start` - just be sure that you're killing the /usr/sbin/sshd process and not one of your sshd login forks at the same time. OK, I've got to be really careful here. I see the following processes in 'ps -ef': root 2988 1 0 Sep04 ?00:00:00 /usr/sbin/sshd root 7573 2988 0 07:28 ?00:00:00 sshd: [EMAIL PROTECTED]/0 Should I: kill -9 2988 /etc/init.d/sshd start Are you sure? :) - Grant -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] awstats
Try changing: ScriptAlias /awstats /usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin/awstats.pl ScriptAlias /awstats.pl /usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin/awstats.pl To: ScriptAlias /awstats /usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin Also I specifically include: AddHandler cgi-script .cgi AddHandler cgi-script .pl I don't know if this is required for awstats to work, but it does for some other scripts. Lastly, make sure that the data directory specified in the awstats config file is writeable by the CGI script. Last, check the apache error logs after trying to access the page and let us know what they say. -Best of Luck, Stephen On 9/9/07, Jason Carson [EMAIL PROTECTED] wrote: On Sun, 9 Sep 2007 21:04:02 -0400 (EDT) Jason Carson wrote: I've installed awstats on my server but when I go to access them from http://canuckster.org/awstats/awstats.pl it says... Forbidden You don't have permission to access /awstats/awstats.pl on this server What do I do? Hi Jay, The obvious questions: What are the permissions? Have you checked the apache logs for messages? I've got it running on a non-gentoo machine. It's in /var/www/mydomain/cgi-bin and permitted as: -rwxr-xr-x 1 root root 527395 Feb 25 2005 awstats.pl* [ HTH, David I have the same permissions. I also have awstats.pl in two locations... 1)/var/www/localhost/cgi-bin/awstats.pl 2)/usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin/awstats.pl I think the second one is what matters, here is part of my /etc/apache2/vhosts.d/00_default_vhost.conf (apache 2.2.6 released today) Alias /awstats/classes /usr/share/webapps/awstats/6.5-r1/htdocs/classes/ Alias /awstats/css /usr/share/webapps/awstats/6.5-r1/htdocs/css/ Alias /awstats/icons /usr/share/webapps/awstats/6.5-r1/htdocs/icon/ ScriptAlias /awstats/ /usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin/ ScriptAlias /awstats /usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin/awstats.pl ScriptAlias /awstats.pl /usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin/awstats.pl Directory /usr/share/webapps/awstats/6.5-r1/htdocs Options None AllowOverride None IfModule mod_access.c Order allow,deny Allow from all /IfModule /Directory Directory /usr/share/webapps/awstats/6.5-r1/hostroot/cgi-bin Options ExecCGI AllowOverride None IfModule mod_access.c Order allow,deny Allow from all /IfModule /Directory -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] SSH won't restart
Yes. As a personal preference I don't usually chain commands together when trouble shooting something, but there is technically nothing wrong with doing so. -Stephen On 9/10/07, Grant [EMAIL PROTECTED] wrote: This process is the ssh daemon: root 2988 1 0 Sep04 ?00:00:00 /usr/sbin/sshd Two things: before killing the process with the KILL signal, I would try killing it with TERM kill -TERM 2988 If that doesn't work then kill the process with the KILL signal. I would also use: /etc/init.d/sshd restart This will give the init script a chance to do some cleanup work before restarting Do this: kill -TERM 2988 /etc/init.d/sshd restart and if that doesn't work, do: kill -9 2988 /etc/init.d/sshd restart ? - Grant I just upgraded ssh and when I try to restart I get: * Stopping sshd ... [ !! ] I don't see anything about it in '/var/log/sshd/current'. How can I figure out what is wrong? I'm a little nervous because I don't want to shut myself out of this remote server. I had a similar issue after a previous update to ssh when I went to restart it to get it to use the new binaries. One of the nice features of sshd is that your current session will say active even if you kill the sshd daemon process. Of course, if you get disconnected then you will not be able to log back in, so it's good to do what you need to quickly if you do need to kill (or if it's really stuck, kill -9) the process. When I had this problem I issued a `kill -9 PID_NUMBER /etc/init.d/sshd start` - just be sure that you're killing the /usr/sbin/sshd process and not one of your sshd login forks at the same time. OK, I've got to be really careful here. I see the following processes in 'ps -ef': root 2988 1 0 Sep04 ?00:00:00 /usr/sbin/sshd root 7573 2988 0 07:28 ?00:00:00 sshd: [EMAIL PROTECTED]/0 Should I: kill -9 2988 /etc/init.d/sshd start Are you sure? :) - Grant -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] SSH won't restart
Killing the ssh daemon does not effect any of the existing connections. The ssh daemon is used to listen for new connections and create a process to handle communications with that request. That is why when you update configuration parameters for sshd, they do not take effect until the next connection. The problem with connecting to the server via telnet is that your password can be easily intercepted - which is one of the major reasons telnet has been depreciated. -Stephen On 9/10/07, Arturo 'Buanzo' Busleiman [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Grant wrote: Should I: kill -9 2988 /etc/init.d/sshd start Are you sure? :) Sounds scary to kill sshd remotely, specially over ssh :P That's why I usually have a telnet server up during ssh upgrade times. - -- Arturo Buanzo Busleiman - Consultor Independiente en Seguridad Informatica Servicios Ofrecidos: http://www.buanzo.com.ar/pro/ Unase a los Foros GNU/Buanzo - La palabra Comunidad en su maxima expresion. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG5Yd+AlpOsGhXcE0RCqCvAJ46Spe77Qukj5oYjCAtBK4lO0cZ4QCcCm24 U/zSADTHUKzZZ/G2dkZZkbo= =5uQv -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] SSH won't restart
I think that there may be something significantly wrong with your box (or configuration of sshd). I have never had a server disconnect an active connection when killing the ssh daemon. If there is someone that you can contact in the data center I would ask them to: 1) Backup your current sshd_config file 2) Restore the default sshd_config on the box, and then try restart the daemon Are there any other applications that are not behaving correctly? -Stephen On 9/10/07, Grant [EMAIL PROTECTED] wrote: Yes. As a personal preference I don't usually chain commands together when trouble shooting something, but there is technically nothing wrong with doing so. And now I'm locked out. What do you think guys? - Grant This process is the ssh daemon: root 2988 1 0 Sep04 ?00:00:00 /usr/sbin/sshd Two things: before killing the process with the KILL signal, I would try killing it with TERM kill -TERM 2988 If that doesn't work then kill the process with the KILL signal. I would also use: /etc/init.d/sshd restart This will give the init script a chance to do some cleanup work before restarting Do this: kill -TERM 2988 /etc/init.d/sshd restart and if that doesn't work, do: kill -9 2988 /etc/init.d/sshd restart ? - Grant I just upgraded ssh and when I try to restart I get: * Stopping sshd ... [ !! ] I don't see anything about it in '/var/log/sshd/current'. How can I figure out what is wrong? I'm a little nervous because I don't want to shut myself out of this remote server. I had a similar issue after a previous update to ssh when I went to restart it to get it to use the new binaries. One of the nice features of sshd is that your current session will say active even if you kill the sshd daemon process. Of course, if you get disconnected then you will not be able to log back in, so it's good to do what you need to quickly if you do need to kill (or if it's really stuck, kill -9) the process. When I had this problem I issued a `kill -9 PID_NUMBER /etc/init.d/sshd start` - just be sure that you're killing the /usr/sbin/sshd process and not one of your sshd login forks at the same time. OK, I've got to be really careful here. I see the following processes in 'ps -ef': root 2988 1 0 Sep04 ?00:00:00 /usr/sbin/sshd root 7573 2988 0 07:28 ?00:00:00 sshd: [EMAIL PROTECTED]/0 Should I: kill -9 2988 /etc/init.d/sshd start Are you sure? :) - Grant -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] SSH won't restart
Yes, accessing the machine via telnet over an encrypted VPN connection
is a safe way to access the box, but given the setup that Grant was
describing it did not sound like he had a encrypted VPN setup to
telnet over.
I also agree that having a secondary way of accessing the box, that is
secure, is an important factor when updating a remote server (whether
that be another encrypted connection or people you can contact locally
in the data center). Other people had already suggested starting a
copy of the server manually on the a different port.
For Grant:
I reread the init script for sshd, and I know see what was most likely
the problem. The init script, now, tries to kill all instances with
the process name of sshd, not just the daemon (as specified by the pid
file). This is why you were locked out when trying to restart the
daemon. If you can restart the machine, everything should be working
fine after a reboot. This behavior differs from every other distro of
linux that I have used, and with previous versions of the init script.
Sorry I missed that before emailing the list last time.
Complete Side Note:
Does anyone know where to issue a bug report to try to have this
behavior changed. The correct (and more widely) seen behavior of
restart for sshd should be something similar to:
start-stop-daemon --stop --quiet --oknodo --retry 30 --pidfile ${SSHD_PIDFILE}
On 9/10/07, Arturo 'Buanzo' Busleiman [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Stephen Wittig wrote:
Killing the ssh daemon does not effect any of the existing
connections. The ssh daemon is used to listen for new connections and
create a process to handle communications with that request. That is
why when you update configuration parameters for sshd, they do not
take effect until the next connection.
In an ideal world, yes. But humans tend to make mistakes. Grant is now
locked-out of his system
because of messing around with conditional execution, kill and sshd all in
the same command.
The problem with connecting to the server via telnet is that your
password can be easily intercepted - which is one of the major reasons
telnet has been depreciated.
I use it over openvpn ;)
COme on, 13 years of using Linux, I should've learned a couple of tricks
already :P
- --
Arturo Buanzo Busleiman - Consultor Independiente en Seguridad Informatica
Servicios Ofrecidos: http://www.buanzo.com.ar/pro/
Unase a los Foros GNU/Buanzo - La palabra Comunidad en su maxima expresion.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG5ZixAlpOsGhXcE0RCiyMAJwNTQKn52VKaHS+/uwGkOYQSuqB+gCfcMSn
fhr6kAdDLTDVAF63dLxFgv0=
=GMM7
-END PGP SIGNATURE-
--
[EMAIL PROTECTED] mailing list
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] SSH won't restart
The current init script will not try to restart the daemon if everything does not exit cleanly. We already know that the main process won't exit cleanly since it was manually killed. Unless you are comfortable editing the init script I would suggest: 1) Type: ps auxww |grep /usr/sbin/sshd |grep -v grep This will give you the process id of the current sshd daemon. Write it down for later use. 2) On the following page, do steps 1 and 2 (I know this article is specifically related to upgrading sshd on redhat, but these steps are the same for gentoo): http://www.hackinglinuxexposed.com/articles/20020319.html This will give you a temporary sshd server, so that we can kill off all of your old sshd process, while still giving you access to the machine. It will also make sure that there are not any configuration problems with your current sshd_config file that are preventing the daemon from starting. If this copy of sshd daemon won't start then we know the problem is a configuration error or that the binary somehow became corrupted. 3) Kill off the current sshd process from step 1 kill -TERM sshd_pid -- or -- kill -KILL sshd_pid 4) Type: /etc/init.d/sshd zap DO NOT USE the stop or restart commands - they will kill off your temporary ssh server from step 2 5) Type: /etc/init.d/sshd start 6) Try connecting to your server as you normally would. If everything is working, then your can kill off the ssh daemon running on the alternate port. If it still doesn't start then its off two round three problem solving... -Good Luck, Stephen On 9/10/07, Grant [EMAIL PROTECTED] wrote: For Grant: I reread the init script for sshd, and I know see what was most likely the problem. The init script, now, tries to kill all instances with the process name of sshd, not just the daemon (as specified by the pid file). This is why you were locked out when trying to restart the daemon. If you can restart the machine, everything should be working fine after a reboot. This behavior differs from every other distro of linux that I have used, and with previous versions of the init script. Sorry I missed that before emailing the list last time. That's alright, I really appreciate your attention. One thing though. Your init script discovery doesn't explain why sshd wouldn't restart (stop actually) when I was logged in does it? Given that, do you still think restarting is the way to go? I'm just trying to make sure I don't restart and still not have access. That would be bad because there is a crucial daemon running now that won't come up automatically. Please tell me what you think. - Grant -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] SSH won't restart
Complete Side Note: Does anyone know where to issue a bug report to try to have this behavior changed. The correct (and more widely) seen behavior of http://bugzilla.gentoo.org I guess. Now, I know why I have never tried to submit a bug report before :) -- [EMAIL PROTECTED] mailing list
