Ubuntu Servers :: Server 10.04 Does Not Start Init.d Scripts?
May 17, 2010
I have two ubuntu servers. I have upgraded them to 10.04. Now I have serious problems at startup: iscsitarget and heartbeat scripts do not start all the times I reboot.I have installed monit to try to start iscsitarget and heartbeat and guess what? It does not start too at boot.In one of the two server sometimes it also starts with ethernet cards swapped.
I installed squid on my machine, and for a while it was starting up automatically when the computer would turn on, and I would only have to reconfigure on ip-up for the new dns, etc.Now for some reason, I notice that squid isn't even started.To fix this, I wrote a start up script in /etc/rcS.d/ that runs:/etc/init.d/squid3 startAnd I notice it still isn't starting.So I write "/etc/init.d/squid3 start" and put it in my ip-up.d/ script.Everything in the script is being executed, but the squid server.I've tried reinstalling squid... what am I missing? where does the computer start these services?
I have installed the Apache Directory Server (ApacheDS) Now I need a iniscript that startining the App as Root, so that it can use the Port 389. After them a unprivileged User (apachds) should run the Service. The same solution I am searching for Glassfish. What can I use for them? RHEL and compatibles doesn't have a start-stop-daemon like Debian.
installed lenny and am trying to install brother dcp7010 again:
1) i can't start CUPS server with /etc/init.d/cups restart "file not found", there is a cups@ link in /etc/init.d.
2) when i install dcp7010 cupswrapper
dpkg -i cupswrapperDCP7010-2.0.1-2.i386.de it ends with " lpinfo: Verbindung zum Server nicht m�glich: Verbindungsaufbau abgelehnt lpadmin: Verbindung zum Server nicht m�glich: Verbindungsaufbau abgelehnt" (connection to server not possible, refused)
3)[URL] doesn't work.
4)foomatic-gui can't find the installed dcp7010 lpr-driver
brdcp7010lpr-2.0.1-1.i386.deb, (a couple of days ago it did)
This is frustrating because it worked in etch and worked for awhile in lenny. The dcp7010-scanner does work.
I'm currently running SUSE 11.1 and trying to start Amavis so I can use Kmail. I have just run the latest updates via Yast. I'm getting the following when I try to start Amavis: /etc/init.d/amavis start returned 7 (program is not running):
Long-time linux user, new to Ubuntu (mainly a gentoo user). I need to get tor and privoxy up and running for a less computer-capable user. I installed Tor and Privoxy, configured them (apparently correctly) and they both appear to work just fine when I start them manually from their init scripts:
However, I cannot seem to get privoxy to start up properly when the machine boots. Tor starts up and waits patiently, but privoxy is dying or getting killed for some reason I can't understand, and on Ubuntu, have no idea how to diagnose. There's no privoxy process after booting, and the init.d script reports status: not running. I have the startup scripts for both Tor and Privoxy linked to in all the relevant runlevels. I played with the order thinking it might be a dependency thing. Hell, I even put a line in rc.local to try and force it to go. But no matter what I do, I can't seem to get the privoxy service to start for me any way but by manually typing 'sudo /etc/init.d/privoxy start' in a terminal, after logging in.
1. Help me get privoxy to auto-start during init
2. OR Help me figure out how to figure out how to get privoxy to auto-start during init. On Gentoo, all of the init scripts are listed on the screen during init as they run, and you can even run through them interactively by pressing I during startup. I have no idea how to do this on Ubuntu. I modified the kernel line to remove the splash screen, but the information Ubuntu puts on the screen during init is quite haphazard. How do I figure out what's going wrong with the privoxy init script?
I just installed Kubuntu (10.04), did some upgrades and updates then upon booting the computer wont go beyond the login page. at first it posted a message (Xsession:warning: unabele to write to /tmp; X session may exit with an error).I followed some instructions from the net which asked that I do the following:
ctr+alt+f aptitude clean of apt-get clean cd /var/log
[code]....
after this, when I login it no more goes off, but the desktop wont still come on, instead a terminal (konsole) window is open but when I try start x it refuses.(the only method I use to start my computer successfully is though the recovery mode)
My desktop server serves up files via a number of protocols and I connect to it via SSH and Avahi. Today I tried connecting to it via SSH, but it timed out. I was able to ping it, and a port scan reveals all the ports I have open on the network. THe problem is that I can't connect via SSH, HTTP, AFP, SMB or any other protocol I have established.Is there a way to jump start a system in a situation like mine? I have a 6 month uptime going, but I'm taking it down soon for some hardware upgrades, so a hard restart is not out of the question, but I'd rather not. I also reset the router without a solution.
Ok so I followed the instructions here [url] and this works great for the install however if the machine is rebooted the VMWare server refuses to start back up stating that it knows that its installed but it was not installed with the right installer.
This is on a Dell Server I can't remember the model right now but its got Dual PIII in it. I'm running Ubuntu Server 32bit 10.10 on the box as well. Thank you in advance for your assistance with this. Once I get this first server figured out I'll get my other one fired back up.
I am trying to make start an iptables.cf script on my server.
I have copied it into /etc/init.d/ And try to make it load with /etc/init.d/iptables.cf start Then "not permission" (I was the root then). So, sudo /etc/init.d/iptables.cf start Then, "command not found".
How would I get the SSH server to start before I've logged in?Basically, the problem I have is that if I'm connecedt to my computer remotely over SSH, and reboot the machine, I'm not able to SSH back in after it restarts. As far as I can tell, this is because the SSH server doesn't automatically start up until after I've logged in for the first time.How would I get around that? Surely that is a fairly common scenario for network admins (especially ones who have keyboardless and monitorless machines running).
Also, doing /etc/init.d/start/ gdm3 says Starting GNOME display manager: gdm3 but it doesn't do anything. I tried pressing ctrl+f1 all the way to ctrl+f12 and nothing. What does work however is sudo gdm3 (with the "ati"/"radeon" driver --- nothing works at all with fglrx).
I am trying to get fglrx working because I want to fix this compiz issue I've been having here which could be related to the shortcomings of the "ati"/"radeon" driver: viewtopic.php?f=10&t=40991&p=312577#p312577
I've kinda gone hopelessly lost on my mail server install and now want to start from scratch, after having wasted 4 days on this.Basically I have a 95% working postfix installation, a probably 100% working dovecot installation, but am not happy with it as a few things aren't working properly, and I don't know what I did!mail to /var/mail/richard NOT /Maildir - being the main oneBut, also the fact that I don't know where I went wrong, and want to understand why everything is now haywire. I am not certain if my security is working on the mail or the logins either.e to achieve is thefollowing:PostfixDovecotVirtual Users - using IMAP with Security, allowed to send mail from their clientVirtual DomainsPostfix AdminWebmail (Roundmail)Anti-Virus and Spam-filteringI started with this guide How to set up a mail server on a GNU / Linux system), which seems very, very good I might add, but it is for Courier, and when I bumbled along with the Dovecot equivalent ... that is where things broke.
I am using Ubuntu 10.04 LTS. Two days ago I updated using update manager. After that I can not boot Ubuntu. When I trying to boot system showing message " Ubuntu is running in low-graphics mode Your screen, graphics card and input device settings could not be detected correctly. You will need to configure these yourself" But I can not configure it.I can not boot to 'recovery mode' also
/var/log/boot.log
Code:
fsck from util-linux-ng 2.17.2 /dev/sda6: clean, 304282/1680960 files, 2964945/6723194 blocks init: Failed to spawn ufw pre-start process: unable to execute: No such file or directory
I start to build up IMPS to my server. Any ideas where to start? Any experience so far. I this think yamicocom like service. And about 5 bugs to get in. What you think? I need to put some extra to this basic concept.
I installed the latest Debian on a computer to make a backup appliance. No GUI.When the computer starts, everything is okay. The DHCP client is running, the network interface have an address, fine.If I do a /etc/init.d/network restart (or stop + start), no more DHCP client. t is stopped when the interface is down. When the interface is up, I have to start it manually.1 - is it normal ?2 - isn't ifup's job to launch the dhcp client ?3 - can /etc/network/if-up.d be the right place to resolve this ?
I have a headless Ubuntu computer which is primarily use as a server but which has Ubuntu desktop edition installed. I use X forwarding through SSH occasionally to use GUI programs so I am not looking to remove them. However, I would like to disable any GUI elements that would be started automatically when the computer is booted. Is the graphical login screen the only thing that would be run? or is nautilus, gnome-session etc. started as well? How would I go about removing the necessary entries from the init scripts?
I just installed ubuntu 10.04 on a pc... the server edition. i went to restart samba and it is not in the init.d directory. is there a different folder for server plateforms? cause im use to my 9.10 desktop edition.
also one more question, when i "ls" the /ect/ directory of course i cant see the whole thing because my monitor only shows the bottom of the file, is there a way to list it like the "more" commands, or possibly scroll up?
Problem I have is the Samba server, it does not seem to start up the shares at boot.When I boot the system, nothing is available on the network, I have to run the Samba Server Configuration Tool everytime I want to access a share, edit a share, save and quit, then my network shares become available.I see Starting SMB services during boot up, it says OK.It worked good on Fedora13.
Has anyone got a working apache upstart script? I'm running 10.04, and want the nice supervision stuff from upstart to run my apache instance. I've googled (especially for things like replacement-initscripts) but not hit anything concrete.
I wrote a custom init script for a java application. The script resides in /etc/init.d and follows the convention for the init.d scripts. However, the script runs the java process as root. I need these processes to run as a non-root user. Is there a way besides using sudo or su in the script (seems inelegant), to run the script as a specific non-root user? Perhaps using a .conf file in /etc/init or a daemon wrapper? What would the Ubuntu way of doing this be?
Before i set up the raid, but with this exact partitioning, the system booted perfectly. When i installed mdadm and created the raid1 mirroring on sda6 and sdb1, the init got screwed up, and all i get is a shell on initramfs, from where i can inspect that sda is binded on md, and cat /proc/mdstat tells me that i have an inactive sda[4].I can't mount the root partition (sda2), because it's busy (i suspect dmraid to lock it), which is, i guess, why init cannot be found.
I wonder if my error is to setup a raid array using a logical partition contained in an extended partition (but i hardly see why it would not work - but the sda bind and the sda[4] in mdstat seems to tell me that it does not), or it's just the initrd that is improperly configured. The other things that bothers me, is that changing the partition type of the raid partitions (fd to 0 - Empty), to disable raid autodetection, resulted in the same behavior on boot. Which might lead me again to think about configuration file problem instead of improper setup.The live cd doesn't not seem to recognize raid, so i can't inspect problems any further, but i could inspect system configuration, but i don't really know where to start.