Hot answers tagged service
This means the service was running at one time, but has crashed. When you start a service, it creates a "lock" file to indicate that the service is running. This helps avoid multiple instances of the service. When you stop a service, this lock file is removed. When a running service crashes, the lock file exists but the process no longer exists. Thus, ...
There are basically two different approaches: Initially start running as root, bind to the privileged port, and then drop down to an unprivileged user. inetd, or xinetd runs privileged, and forwards the requests to web server running unprivileged.
You can use: ifdown eth1 ; ifup eth1 As a single command. The ';' just runs one command, then the other. As long as your interface is configured to have the neccessary IP and route to match the current configuration, your ssh connection won't drop. If you're worried about using it on a production server that you don't have another method of access to, ...
From the man page: service runs a System V init script in as predictable environment as possible, removing most environment variables and with current working directory set to /. It then calls the init.d script. So they both accomplish the same thing, except calling the script via /sbin/service just ensures that some environment variables in your ...
If the service is starting and terminating improperly then you don't need a script to do this. Open the Services control panel Right-click on the service and get properties Click on the Recovery tab and edit the settings there EDIT: Yes, and as everyone has added you should certainly be checking to see what is going on with the service. Travelling Tech ...
http://sdf.org Have used an account here on and off over the years. Recommended!
You can use SC to create user defined services. This command will create a service: sc.exe create "Service Name" binPath= "C:\Your Program.exe" Note there must be a space between binpath= and the program location. To Delete the service use: sc.exe delete "Service Name"
Updating that file and then restarting the service is the only way. You can push a new file and then make the service Require that; that way when the contents are updated the service will properly start. If you don't want to replace the file entirely you can use the Puppet augeas tool to just modify the single line in the defaults file. There are a few ...
Seems like the wrong solution, somehow. If you're on Ubuntu, use Upstart. If you're on Centos/RHEL/Other, take a look at using start-stop-daemon and the LSB init standard to properly daemonize a process, and then that'll enable you to use chkconfig to start/stop it automatically.
monit is a great way to monitor and restart services when they fail--and you'll probably end up using this for other essential services (such as Apache). There's a nice article on nixCraft detailing how to use this for services specifically, although monit itself has many more functions beyond this. As for the socket aspect, @galraen answered this spot on. ...
Snarky Answer: DNS does not do URL forwarding. DNS has no knowledge of this "301 Redirect" of which you speak, and has no interest in your H-T-T-P verbosity over on port 80, nor these you-are-ell thingies - it only knows name, address, and maybe a few other important conversational words like "food", "bathroom" and "penicillin" . Non-Snarky Answer: You ...
The primary problem is that there is no proper $PATH defined in the run environment of cron, so you need to use the full path to service for this to work. You can find out this path with the command which service, which should print something like /usr/sbin/service. The secondary problem: I wouldn't do that, just blindly restarting services on a ...
From a command prompt running with admin credentials: sc config <server_service_name> depend= <database_service_name> Read more at this sc.exe documentation.
Check out the Free Shell Accounts list.
I'm not sure how I can contact you 'off-site' but for the purpose of the thread, here are the basics: 1) Disable unnecessary services. Ubuntu isn't my strongpoint, but, I believe debian systems use 'rcconf' to switch off services. You can also modify the files directly in /etc/rc.d. You don't want to run anything that could leave you vulnerable, or require ...
For the hell of it I checked a few of the standard daemons on my 12.04 machines. You have to manage the file, no way around it at this point in time. snmpd # snmpd control (yes means start daemon). SNMPDRUN=yes collectd # 0: start collectd on boot, 1: do not start collectd on boot # default: 0 DISABLE=0 puppet # Start puppet on boot? START=yes ...
The service --status-all command tries to figure out for every init script in /etc/init.d if it supports a status command (by grepping the script for status). If it doesn't find that string it will print [ ? ] for that service. Otherwise it will run /etc/init.d/$application status. If the return code is 0 it prints [ + ]. If it's not 0 it prints [ - ]. ...
I would also check the Event Viewer to see why the service crashes - it could be that a minor fix, or a driver update would solve the problem permanently.Another point: if the process leaks memory and leaves allocated memory behind when it crashes, restarting it over and over decreases the OS stability and increases the chance your entire system will run out ...
You can call setsockopt(2) for listening socket with SO_REUSEADDR, so you will be able to bind(2) it again without waiting for expiring all connections. Another possibility: drop connections from kernel. FreeBSD have tcpdrop command for this, don't know about Linux.
You should be creating an init service. Ubuntu uses upstart. http://upstart.ubuntu.com/
Drop the pipe to find. Irritatingly, the application is on a new line, so you can't use the find utility. For example: C:\Windows\system32>netstat -abn | find "3306" TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING TCP [::]:3306 [::]:0 LISTENING And without the pipe to find (snipped for brevity) ...
Check out TCPView http://technet.microsoft.com/en-us/sysinternals/bb897437 TCPView is a Windows program that will show you detailed listings of all TCP and UDP endpoints on your system, including the local and remote addresses and state of TCP connections. On Windows Server 2008, Vista, and XP, TCPView also reports the name of the process that owns the ...
chkconfig essentially makes a symlink from, say, /etc/rc3.d/S85myapp to /etc/init.d/myapp. Verify that those links exist. I assume they do, since the "chkconfig --list" is showing that they're "on". Since you can execute /etc/init.d/myapp from prompt, but it doesn't occur during startup, my guess is that there's an issue with the PATH, or that a service ...
While I don't have the WSFP installed here, by far your best bet is to use WebSphere's versionInfo utility. You can find it in %APPSERVER%/bin where %APPSERVER% is your WAS installation location. Reference (from the WAS 6.1 infocenter) can be found here. My suggestion is that you generate the version report in HTML using the most detailed flags (-long ...
Your symlinks are there, but they're not what you want. If you notice, yours are all prefixed with 'K' for kill. They should be 'S' for start. Fix this with chkconfig beanstalkd on and verify it with chkconfig --list | grep beanstalkd.
You can use windows task scheduler to run net start service and net stop service at the appropriate times.
Monit is a relatively easy to configure service that will restart services (and more).
DJB's Daemontools can do exactly what you want. However, it would be more productive in the long run if you could figure out why things are dying and fix the cause, not the symptom.
It's hard to say this without sounding flippant, but the error message is telling you what to do. The first place you should be going, on a Windows NT-based operating system (like W2K3), when you're sorting out misbehavior with the OS is the event log. Doubly so when the error message tells you to do that. Some service or driver program marked for ...
Only top voted, non community-wiki answers of a minimum length are eligible