and nothing is working I tried to reboot or top command but not working also I can't open SFTP the server says The server has rejected the SFTP request.
I need help adding a nohup command in this command line: su - rhx12 -c "/rhythx/rhythx/bin start /rhythx/rhyth" When I execute the script using root on the command line it works fine. But, when I reboot the server the process doesn't start. This script will go into the etc/init.d and rc2.d directory.
#!/bin/bash case $i in start) su - rhx12 -c "/rhythx/rhythx/bin start /rhythx/rhythx" ;;
I am using sda1 as /, which is a bootable drive. I do not know if my problem is that I did not create a /boot drive. After removing the iso dvd, I tried to reboot and I get this back: -bash: /sbin/reboot: input/output error Then it returns me to the terminal prompt.
I have one server with Jboss and Tomcat installed, I have to start these servers manually everytime I do reboot the server.How I could do to start Jboss and Tomcat automatically, when I do reboot the server?
If I make a cronjob to reboot a server every 3 days at like 2am? This way it will free up ram, etc and cause less problems right? I know a guy that is doing this, and I'm trying to convince him otherwise.
I have installed Ubuntu Server 10.04 on a Dell pc without issue, but on reboot or startup from being off it doesn't load the os. It flashes error: no such disk then leaves me a blank screen with a flashing cursor. For some reason it's not seeing the drive.
I've been pulling my hair out on this one. I haven't had to reboot my server in many many moons, but when I did recently, everything fired back up just fine... except httpd!The strange thing is that if I log in after reboot and simply type:
If I can remotely reboot a server using SSH over CGI? I configure the client and server with keys to make ssh without password, and, on the terminal i can make "ssh root@server_ip reboot" and it reboot normally, but, I don't know how to do this on a CGI?
I have been running Fedora 12 on my HP Proliant DL140 Server for about 6 months now without any issues, yesterday I ran yum update and rebooted afterwards but the server now wont boot
After a couple of days, some commands related to the disk (df) or files (ls) or killing process (kill -9) doesn't respond. Even I can't reboot or shutdown my server. After an hard reboot, some files are not here anymore or the log files are not filled anymore until I restart.My disk are behind the RAID controller i6 and are configure in RAID 1. The disks are two HP SCSI 72,8GB 10k RPM.Maybe I am totally wrong to check the disk access side, so I am open to other explanation.I can also add that my CPU is running under 1% et my RAM under 10%.
service xend status returns nothing - simply moves to next line service xend start does the same thing xm list ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Error: Unable to connect to xend: No such file or directory. Is xend running?
I had recently setup an OpenVPN server on x64 10.04 via the guide found at: [url]
Everything was working perfectly, all clients were able to connect etc.
Today I needed to reboot for a completely unrelated issue - only to find that upon logging in, openVPN was no longer running.
When I tried to execute 'sudo /etc/init.d/openvpn start' I'm presented with an interesting message...
This *used* to say Server. I've double checked all the configs and scripts used in the config and they all check out OK. I purged and reinstalled openVPN to no avail...
i've installed 11.04 server on my macmini 3.1 (late 2009) from cd, and it is the only system isntalled (no os x, no windows). It works very well, even netatalk. The problem is, if i reboot the computer ubuntu doesn't start and i've got the blinking folder with question mark after ~30 seconds.
I installed 11.04 server and had samba share /tmp (as advised by the server pdf doc) shared to my windows 7 laptop, which was all well and good, so copied some files to it and rebooted the server, and they had been removed.i guess i shouldnt have put anything in /tmp as i presume this is cleared on reboot, so why did the documentation advise to create /tmp share?
We have a server running suse 9. I had to do a reboot yesterday. the server dropped off the network, but did not reboot. It was attempting a connect, but I don't know why or to what. These are the lines that I saw on the screen:Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1) ))
I want to make sure sshd service will start after a server reboot. On redhat or centOS I can do "chkconfig sshd on". What's the equivalent command for ubuntu?
We have three production websites running on RHEL 3 AS running tomcat 5. After a reboot last night Tomcat will not start and has the following in the catalina.out log:
Mar 20, 2011 4:09:31 PM org.apache.commons.digester.Digester startElement SEVERE: Begin event threw error java.lang.NoClassDefFoundError: org/apache/naming/resources/ProxyDirContext at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) at java.lang.Class.newInstance(Class.java:308) .....
I have spoken with our Java Developers and they seem to think it is something up between httpd and tomcat at an OS level. Since Tomcat is not starting and giving an error that it is all ready running, I think you have a stale lock file. Look for the file /var/run/tomcat5.pid and cat or less it to see what the PID number is. If it matches the error, then delete the file and try to start Tomcat again. It should start this time.
Most common problem with Tomcat5. Try following : 1) Search PID in /tmp, if found delete it or else stop your tomcat. 2) Undeploy your application 3) Check out this link [URL] to know what causing tomcat to generate this error.
If none of them work then check your application configuration settings. [URL]. When I do start tomcat it appears to start:
[root@RPSI-2 san00]# service tomcat5 start Starting tomcat5: Using CATALINA_BASE: /usr/share/tomcat5 Using CATALINA_HOME: /usr/share/tomcat5 Using CATALINA_TMPDIR: /usr/share/tomcat5/temp Using JAVA_HOME: /usr/java/jdk1.6.0 [root@RPSI-2 san00]#
But then I try to find if it is running via ps -ef | grep tomcat5, I only receive my query. I perform the same query on Java and it also only returns my query.
We rebooted the server and getting: BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu7) Built-in shell (ash) Enter "help" for a list of built-in commands. (initramfs) When we boot from the live CD to run fsck manually, it cannot find the hdd partition. It's using Lilo boot loader.
Few days ago we had a server maintenance. The system was shutdown, we fix the CPU fan, and start the system again. But somehow when the system starts, our IMAP server - dovecot is not running. It just sit like a rock. Because the machine had a CPanel/WHM, I tried to restart dovecot using cpanel and got a message:
Code:
That was not really useful....
When I tried to restart dovecot using command line, I got nothing. really nothing.
Code:
How to find out what happens to my IMAP/dovecot? And anyway to make it run again?
I am having a Xen server xend daemon is taking care of giving interface names like vif1.0 or vif0.2 to the connected guest operating systems on it.I can not save the current IPTABLE rules since upon reboot the xend daemon gives different names to virtual ethernet interfaces i.e. vif1.0 or vif3.0 or vif9.0 like that.I have some rules that I want to be active upon subsequent reboots and not all.Say for example an SSH to external server at port 8000 should forward the request to a machine on LAN.Which I have done by port forwarding from IPTABLES.So I need to save some rules.I was thinking to make a script which on reboot activates those rules.
I am not clear on where to do that.I came across internet and found /etc/network/if-up.d/I am not clear with this directory my question is if I make a scrip which has IPTABLE rules as I want and save it in above folder will it work. I am not clear with what is /etc/network/if-up.dfor.Suppose my logic is wrong then how should I go for it.Also I want to know does a protocol uses two port to make a connection.I have forgotten that thing,i.e if I run an SMTP or ssh then do they use port 22 and 23 both in case of ssh or 25 and 26 both for SMTP like that or just specifying the rules for one port will be enough.I tested these rules in a secure environment where i had disabled firewall and ssh forwarding on router worked well
I am using RHEL 5.4 my root password is getting reset after every reboot.every time i had to change the password from kernel to access the root.i am unable to find the where the problem is.
I have installed FreeRadius to a Debian Linux server.I have configured an account called Support to run the Radius as I didn't want Root to be the user to run this.I want Radius to start up automatically after the system is rebooted but I don't know how to do this. I am new to Linux so please bare with me. If the system is rebooted, is it possible for the Support account to be logged in automatically? Is there a script I can create to automatically login the Support account? This may not be secure but it has been requested. Also the main question is after a reboot can the Radius be configured to automatically start without the need for someone to login? So if the system is rebooted and then goes back to login prompt, can the Radius then be running?
I have had a good search about scripts but with my limited knowledge it isn't too easy.
After reading it also said something about using rc.radiusd which will automatically start Radius after a reboot, but again I cannot understand exactly what I need to do.Please can someone help out with this and let me know if I am on the right track? Will the start-my-radius.sh script work after the system is rebooted without someone actually login and how do I get it to work?Please explain clearly as this is all a bit technical for my liking and not understanding it well!
I'm running a CentOS 5.2 vm on a W2K8 hyper-v core server. The problem I have is that when I reboot, the system time always resets itself to 6:00 am in the morning. I tried the /sbin/hwclock --systohc command but it hasn't taken hold.
Further to this LQ thread which Tinkster solved by suggesting the last command (thanks Tinkster) I have been exploring last -x reboot and have found that the reported duration is incorrect for the last reboot and shutdown when a old wtmp file is used. Not having a record for the following shutdown, last assumes that the system has been up until the current time and similarly for the shutdown.
The output comes in time order, latest first, each line showing the time of the reboot and the uptime from then to shutdown. Using last -x reboot shutdown to show the shutdown time, here's an illustration
Code:
shutdown system down 2.6.29.6-smp Sun Mar 7 15:35 - 03:02 (11:27) reboot system boot 2.6.29.6-smp Sun Mar 7 09:35 (05:59) 09:35 until 15:35 is 05:59.
When the uptime exceeds 24 hours it is shown as (<days>+<hours:minutes) like this Code: shutdown system down 2.6.29.6-smp Sun Feb 21 12:39 - 13:20 (00:40) reboot system boot 2.6.29.6-smp Sat Feb 20 09:39 (1+02:59) 09:39 until 12:39 the next day is 1 day 02:59.
The time in parentheses at the end of the shutdown lines is normally the time until the next shutdown.
So far so good. The incorrect output is for the last reboot and shutdown of an old wtmp file. Here's the output of last /var/log/wtmp -x reboot shutdown; last -f /var/log/wtmp.1 -x reboot shutdown
Code:
[snip] reboot system boot 2.6.29.6-smp Fri Mar 12 07:42 (01:54) shutdown system down 2.6.29.6-smp Fri Mar 12 01:31 - 09:37 (08:05) wtmp begins Thu Mar 11 08:25:26 2010 [snip] reboot system boot 2.6.29.6-smp Wed Mar 10 14:12 (15+01:42) shutdown system down 2.6.29.6-smp Wed Mar 10 12:41 - 15:54 (15+03:13) [snip]
The boot started at "Wed Mar 10 14:12" which had an actual uptime of 1 day 11:20 is reported as 15 days 03:13 which is the time from then until the last -f /var/log/wtmp.1 -x reboot shutdown command was issued. The time from shutdown to shutdown is similarly affected.