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.
Where do I change the option to have samba start during the boot process? I've googled and I've found old posts that say it's a line in /etc/rc.d/rc.inet2 but in my semi-current box, I don't see the part about starting stopping the samba server.
I have a file server running samba 3.4.0. I just upgraded ubuntu to 9.10. The upgrade was unfortunately stopped in the middle, but I think I managed to complete it.The problem is that now samba will not work after a reboot. The daemons are running, but any attempt to connect from a windows machine fails (Windows 7: the network path was not found). Manually restarting the service fixes the problem, but I need a more stable solution!Interestingly, I can ssh to the machine, or rdp to a virtual machine running on it.The logs don't seem to report any error:
Each time I boot I have to restart samba to see the shared printer on other windows machine. I tought it was the cups problem listed on the forum, but I'm not sure anymore if it's related!Could it be related to the service sequence? I don't know how to look at the service load sequence in ubuntu?
I wrote a little script that will automatically mount two Samba shares to my home directory and I was wondering if a) You guys/gals had any input as to how I could improve on this script and b) Tell me how I would go about having this script automatically execute when I log on via SSH.
#!/bin/sh mount -t smbfs -o username=Myuser,password=Thepassword //192.168.1.102/Data1 /home/user/Data1 mount -t smbfs -o username=Myuser,password=Thepassword //192.168.1.102/Data2 /home/user/Data2
Ubuntu server 10.04 comes with a new event based startup system, and I wonder if that can be responsible for this problem. The server has been upgraded from 9.10. On reboot mysql does not always manage to start... /var/log/mysql/error.log has info similar to this:
100511 19:05:00 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address 100511 19:05:00 [ERROR] Do you already have another mysqld server running on port: 3306 ? 100511 19:05:00 [ERROR] Aborting
So apparently port 3306 is not 100% unused when mysql tries to open it or somehow network connections are not ready, even if mysql start is supposed to wait for 'net-device-up' and 'local-filesystems' according to /etc/init/mysql.conf. This does not happen on all reboots. I am supposed to be able to start it manually with command 'start mysql' but that does not seem to work also. When I try start it again, it says mysql is running but no databases can be reached and mysqld is not active, reboot and good luck is all that helps...
As far as I know there are no firewalls installed, at least none I have manually configured and it has worked with no problems on 9.10. So this new upstart thing seems responsible. It simply does not let mysql wait until it can start in good way. That also explains why it's a random problem. If all starts happen when and if there is free processor time, it does not always start things in the same order on every reboot. The key here is port 3306, or whatever port mysql is configured to use. The upstart system simply needs delay the start until the port is 100% free and available for the system to use.
I have recently set up my web server using the LAMPP package for Ubuntu. Now I'm running Ubuntu Server 10 so my machine boots into the console and not gdm. Also I have my machine autologin as root so I can simply turn my server on and not mess around with logins. Now I created a simple shellscript for starting lampp and then I put it into etc/init.d/, chmod -x file.sh to give it executable permissions, then I update-rc.d file.sh defaults but nothing happens on startup. It simple takes me to the console and nothing more happens. I have to manually start lampp on every bootup.
Currently when the system boots, It boots jabberd2 before mysql. So jabber fails. Then, later mysql is loaded. I either want to force jabber to load mysql first, or make the system boot mysql first. I've tried changing /etc/init.d/jabberd2 to say "# Required-Start: mysql $network $named $remote_fs"... However, insserv says that mysql service has to be enabled... so I assume that's an issue because mysql is an upstart script.
Running Ubuntu Server 10.04 32 bit. Sometimes when I reboot it does not start up, It seems to be going through the boot process but then just hangs. I have had a look at the log files and can't see anything, but I'm not really sure what I am looking for.
I'm having some trouble with Tomcat 6 after upgrading to 10.10. During the upgrade process, the installer hung while dealing with Tomcat 6, which required me to kill the upgrade and do some clean up, and then re-run `apt-get upgrade` again to get things going. This left some weirdness (like the MOTD for both 10.10 and 10.04 being shown on login), but otherwise things are OK. The only remaining problem I have is Tomcat; it simply won't start when the server is booted. The information I have:
Tomcat 6 runs normally when started with `sudo /etc/init.d/tomcat6 start`. No errors are thrown, everything works as expected.I used `rcconf` to try removing and reinstalling the rc scripts, this didn't help. I manually deleted all the rc scripts, then used `rcconf` again. The scripts all seem symlinked correctly to `/etc/init.d/tomcat6`, but it's just not coming up on boot. I ran `sudo grep "tomcat" /var/log/*.log` to see if something is appearing in the logs, but nothing of interest is there.
How can I verify that Ubuntu is even trying to start Tomcat? As this is a development box, I am not adverse to a quick + dirty solution if there's some either simple way of getting it started at boot. I'm thinking the next Ubuntu release will see me blow away the server and start it fresh, but right now I'd just like a working box
I am having some trouble making the dropbox daemon start at boot. I followed these instructions -> [URL], which are basically a replica of the original instructions from the Dropbox Wiki [URL]. The installation went fine, except that the machine still cannot start the daemon at boot. I tried to modify the init.d script a bit (see the attachment), but it still wont work (I am not sure if my changes made any significant difference, though). The daemon will only start if I invoke it manually after login with the command:
[user@machine:~]$ service dropbox start
Which executes the daemon just fine. I also tried adding this line of code to crontab:
@reboot /etc/init.d/dropbox start
This command starts the daemon if I check with the command "service dropbox status", but if I execute the official dropbox CLI command:
it says that Dropbox isn't running and I still have to execute it manually.
P.s.: The machine runs Ubuntu Server 10.04, with all the latest system patches and updates.
I'm running the host server on Ubuntu 10.04 LTS (64bit) . I'm using virtual box. I want to automatically for one of the guest vritualboxes to start on reboot. Following is already done without a success. Please help me in solving this.
1. I have created the following shell script #!/bin/bash /usr/bin/nohup /usr/bin/VBoxHeadless --startvm "VMNAME" 2> /dev/null &
2.From the current logged on user I did a crontab -e and did the following
crontab -e @reboot /bin/sh /home/myaccount/shellscript.sh note that I do not encrypt the home directory and sufficient permissions are there.
On my Ubuntu 10.04 LTS Server, mysql does not start at boot. I tried this but does not work. Code: root@dev:~# chkconfig mysql ON
The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs. insserv: warning: script 'K02mysql' missing LSB tags and overrides insserv: warning: script 'S10vzquota' missing LSB tags and overrides The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs .....
How to make sure mysql process comes up automatically after every reboot
I have a few problems getting a custom service/daemon to auto-start at boot. I'm running ubuntu 11.04 Server amd64 edition. One of the services is a Teamspeak3 server I'm trying to start. I would like it to start up automatically on boot. ts3 already have a script with start/stop commands so all i have done is make a little script for it to get it to run as the correct user.
I recently upgraded a Ubuntu server from version 8.04 to 10.04 and after a reboot the webmin and syslog-ng server do not start at boot anymore. I can start them manually by doing /etc/init.d/webmin start and /etc/init.d/syslong-ng start and everything works fine until I root again. Granted this machine is rarely rebooted but when it is, I don't want to have to remember to start these services. I have tried a full removal of syslog-ng and reinstall but to no avail. The entries are in the rc directories like they should and the links are valid.
I'm completely stumped by a problem with httpd in Fedora 13. It fails to start on boot: I can see: Starting htpd: FAILED, in /var/log/boot.log, but I can't find anything else in messages, audit.log or anywhere else that gives me any clue why. The weird thing is that running: run_init service httpd start after boot _works_ and the server runs fine, but even when it's running OK, service httpd status reports httpd dead but subsys locked
I'm guessing that the problem somehow relates to selinux, but I can't find anything in the audit logs that gives me a clue. How to turn on more logging so that I can get closer to the problem. I finally discovered the cause. This system was originally configured to use network services directly, without NetworkManager. It had been upgraded a number of times since installation. It seems that over time, if you have turned off NetworkManager, the defaults have changed. Used to be that the network services was 'enabled' by default (hence started at run time). Now, the default is 'disabled'. Httpd couldn't start because there was no network to start on. Enabling network services at boot time fixed this. I guess I should have noticed this. But one might think that httpd failing to start because of the lack of a network might at least give a warning message in the logs about the reason.
I have tried different methods to auto start wpa_supplicant at boot on Ubuntu Lucid server on a laptop which can't be connected to Ethernet.
The only thing that worked is adding the wpa_supplicant command before exit0 in rc.local. It solve my problem of wpa_supplicant auto start and annoyance on not be able to ssh before local login. But the screen stuck at Ubuntu Logo. How can i get pass Ubuntu logo screen to regular tty or xbmc in future?
Can anyone help me with how to create an init.d script that will startup a vm machine in virtualbox at boot? I found this script:[URL]..But it is for ubuntu. I am running fedora 12 x386 and using it as an Amahi server. Very cool, but it would be extra cool if I had a virtual windows machine startup when I booted up this server. Then I could just rdp into it when I needed something in windows.
I just moved my / from sda1 to an ide drive, hde1. i dont see how this could have caused any of these issues, but it did.
First my network card failed to start. i added a line in my rc.local file (where i put all of my additional programs, etc i want to start):/etc/rc.d/rc.inet1
The above now starts my network card with my static ip configured. dhcpcd also worked but i wanted this static.
Now samba will not start. i have the following line in my rc.local: /etc/rc.d/init.d/samba start
This used to work just fine. at first i thought that samba may be trying to start before my network card gets an ip, but the line is *after* the network startup line. just to make sure, i made an additional script called startsamba which contained a sleep 60 followed by samba start, to delay the startup of samba even further.
The message samba reports is very vague, something like failed - core dumped. most of the core dump log is garbage characters, but here is the beginning which seems like it might contain some info:
ERROR: Can't log to stdout (-S) unless daemon is in foreground (-F) or interactive (-i) after the system starts, i can drop to a console and type "/etc/rc.d/init.d/samba start" and the service starts just fine. i've also tried starting samba manually with "smbd -d" which also produces the core dump when started from rc.local, but not when started from a console after startup.
I wish to prevent the samba messages (mainly nmbd and winbindd) from appearing in the system log (/var/log/messages). I want to allow samba logging to the standard samba logfiles, but prevent the syslog getting clogged up by samba. I added syslog = 0 to smb.conf and reloaded the config but the messages were still appearing. I also tried the following (and restarted the syslog via /sbin/service syslog restart) # Suppress messages from samba.
For interests sake the messages I'm getting are below (I'm not concerned about the messages themselves, I can chase them up at my leisure via the samba logs) Mar 18 09:58:29 SERVER nmbd: query_name_response: Multiple (2) responses received for a query on subnet xx.yy.z.zz for name DOMAIN<1d>. Mar 18 09:58:29 SERVER nmbd: This response was from IP xx.yy.z.zz, reporting an IP address of xx.yy.z.zz.
I am trying to get mysql to start at boot without any success.
The mysqld scripts works fine when run from the command line, but it does not work when i use the links created by chkconfig. I checked the boot.log and found that mysql starts but then it stops or gets shutdown. This is the log message:
Starting mysqld daemon with databases from /data/mysql [ OK ] Starting cups: [ OK ] STOPPING server from pid file /var/run/mysqld/mysqld.pid starting DenyHosts: /usr/bin/denyhosts.py --daemon --config=/usr/share/denyho sts/denyhosts.cfg 090727 04:35:47 mysqld ended
I have a mysql database and i use it with apache for my webpages. And I guess it dosen't start when the computer starts so I have to manually start it with "sudo /etc/init.d/mysql start" This returns fail so i went to '/var/run/mysqld/' and the folder was empty. I don't know if this is the problem or not. How can I fix this?