Because of my problem here:[URL]..I'd like to replace upstart with systemd on F14. Is this as simple as a yum install? In the wiki is it's referred to as a "technology preview" for F14, which is meaningless to me; there are no further notes about installing or enabling it.
View 1 RepliesI've proven that the the D in systemD is for DISASTER.At first, I thought that the dozens of problems I had with startup, shutdown, and services, was due to my upgrading from Fedora 14. But now that I've tried a fresh install, I have a new set of different problems. Basically DBUS broke after I installed Samba, and no combo of reinstalling either of them fixed anything. So here goes my third Fedora 15 install.
During a fresh install, can I de-select systemd and select upstart and sysv instead? systemd is not visible in the GUI installer. Do I need some Kickstart hack or something? Is this possible at all?
What is the correct/safe way to move from upstart to systemd? I originally installed upstart in 11.3 and have now upgraded to 11.4. Having successfully upgraded to 11.4 I tried to use yast2 to install systemd and systemd-sysvinit onto my running system. Yast correctly identified that upstart should be deinstalled as a prerequisite for installing systemd-sysvinit.
After the install of systemd the system wouldn't shut down, and on a reset the system reported many systemctl/start service timeouts on things such as mounts and ttys. Eventually the system started an X-windows KDM login, but there were no console ttys and mounts were missing. I used X/kdm to login to root - phew! - I restored / from an rsync backup I'd made prior to the changes, so I'm back in business with upstart. I'd like to tidy up and move to systemd - I going to have a nose around myself, perhaps I will try switching back to sysv init and then going to systemd - but I have to wait for the machine to be idle before I experiment, any info in the mean time would be great.
We have seen with the release of Fedora 15, systemd is the new start-up services, which will replace SysVinit and Upstart on most Linux distributions. Here are some tips based on the order systemd-analyze, for analyzing the startup time of your OS.On commence avec l'option time, qui affiche le temps total de d�marrage de votre syst�me : (One starts with l' option time, which posts the total time of starting of your system: )
Code:
$ systemd-analyze time
Startup finished in 6385ms (kernel) + 3228ms (initrd) + 49335ms (userspace) = 58949ms
[code]....
What's the best way to get a list of the start order of services from systemd? Yes, I've tried
Code:
systemctl --order
This looks like the output I would expect, except that if that list is the system service start order, then my system is hosed. I certainly hope that my system is not starting nfs service before all the /usr/export filesystems are mounted.
I tried
Code:
systemd --test --system
but that generates over 22 thousand lines of gibberish! I filtered that with
Code:
systemd --test --system | grep -- -> | grep Unit | grep -i service
And it's less gibberish, but it's ALMOST the reverse order of the first command, and still pretty crazy.Ultimately, I need to discover, and fix the order of the services started by systemd, because they were mangled during the upgrade from Fedora 14 I hope that "systemctl --order" is either not the real deal, or I'm reading it wrong. Because if it is, I'm afraid I have a huge problem to fix.
Two general questions about Fedora 15 before I decide to install. My system typically starts in about 32 seconds, with a distro using normal boot scripts. With Ubuntu and upstart it reaches the gdm login screen quicker in around 18 - 24 seconds. With systemd does anyone get a noticeable difference?
Also, is it possible to use an alternative desktop to gnome3 in Fedora 15. I've tried Gnome3 with Arch and its very slick although not for me, as I like panels and desktop applets. (I should add that my times quoted were mesaured using bootchart with a default set of services, no tweaking).
it's the installation media or the ISO is broken because i have reburned / redownloaded the fedora14 multiple times with the same result. I even tried burning the disc on a different computer just to make sure the burner is still working. This is the error i am getting when the "Starting installation Process" dialog displayed.
"The file upstart-sysvint.0.65.9.fc14.i686.rpm cannot be opened. This is due to a missing file, a corrupt package or corrupt media. Please verify your installation source" I remember fedora 13 and below i have to use nousb command or something similar to get fedora installed properly but not for fedora 14. It just pops up with the message above.
Can the Replace function replace more than one word with the same character(s)?
Also, do you know how to access the plugins provided by the gedit-plugins package?
I have a problem during BOOT. During BOOT Fedora seems to stop at the following line:
Code: [20.245743 systemd[1]: unit systemd-tmpfiles-setup service entered failed state for more than a minute... and then it resumes.
I seem to be having some issues. I want to do the following. I want a script to run prior to any GUI starting (so that if it does crash close or whatever it is not effected).I am able to run the script after the system is booted and it works exactly as I want it to. Once the GUI opens I have a window open and maximize with no decoraction via devilspie. This way I have a desktop that can monitor the logs but not interact directly interact with the shell which is actually recording the logs.
The problem is, when I try and use a simple Upstart script to start it the script does not seem to be working. If I do a ps -A it seems to be still running. What it should be doing is recording what the serial input to the log file I am using. In fact... it doesn't seem to be capturing anything. If I try and run the script manually after the computer has booted (with the Upstart script run) to a GUI it crashes the system.The script I am running is simply to record any incoming data from a Serial connection. It sets up the serial port then starts recording.The shell script is as follows:
Code:
#!/bin/bash
stty -F /dev/ttyS0 9600 -crtscts cs8 -parenb -cstopb -clocal ixoff ixon
[code]....
Very frustrated. I have used Unix for ages so I understood the SysV startup stuff. But I have not had a lot of luck with Upstart. The other day I noticed that on every reboot my disks are getting fsck'd. I just recently put an ext2 on /tmp so this takes a while (the ext4 drives just rip through their journals).
The problem is no one is unmounting them on a KDE restart (4.X). I started out looking at /etc/init.d/umountfs and putting some logging in there. It never runs. This is despite that /etc/init has an upstart job that is supposed to run all the runlevel stuff.
I also tried to log some info in /etc/init/mountall-shell.conf which looks like it tries to do a umount -a on shutdown (which is probably not a good idea; you need to unmount in a particular order). That doesn't seem to happen either. I am not even sure how to troubleshoot this further. I suppose I need to see if the reboot( command has the same problem. Or if I shut down kdm first if it goes away.
I'm running the new OpenSuse 11.3 64-bit. how to switch from SysVinit to Upstart?
View 1 Replies View RelatedI have run into a problem that I've tracked down to being a conflict between the "Upstart" init system, and how it handles multiple (alias) IP addresses per physical interface. The summary of the problem is that the interfaces are being configured in the background in parallel with the starting of daemons. One "feature" of this (apparently intended for pluggable devices that would add or remove an interface) is that the network daemons are restarted each time an interface is added (and presumably deleted). But this is a disaster when applied to alias IP addresses.
I first saw the effects of this when during booting Ubuntu Server, the screen showed a message about OpenSSH daemon being restarted ... several times a few seconds apart each. At the time I didn't know what was causing that, but didn't worry because it ultimately was running when I needed it.
But now that I am deploying these servers for specific duty with many IP addresses per system (per network interface), the symptoms are becoming serious, and I need a solution.
1. The IP addresses are coming online too slowly. Apparently the time it takes to restart each daemon is being added to each address being configured.
2. It appears to be disrupting some daemons sometimes. Occaisionally, some daemon just ends up being hung somewhere, or dies. Too many restarts.
3. Sometimes few or even no alias addresses get configured. This might be due to a daemon getting hung, and the whole sequence just not finishing.
4. The "nsd" name server as packaged by Ubuntu doesn't deal well with this at all. It needs all its IP addresses to be up when it starts, or else it won't start. The Ubuntu package of it doesn't including any if-up script at all, although I'm not sure that would do any good.
What I need is a way to configure all these alias IP addresses so they are all configured immediately when the point in time is reached to bring up network interfaces for the first time. These are all static, and all are aliases on ethernet NIC cards plugged into PCIe cards, or integrated in the mainboard. None of them are pluggables. I did run a manual test of "ifconfig" in a loop configuring 2540 alias IP address on eth0 and it only took 2 seconds (no if-up triggers or daemon restarts here). So I know it's fast if nothing else is done between these steps.
Even for pluggable physical interfaces, I see no reason to even try to step through every alias (if it has aliases) with a daemon restart. If an alias IP address is added on later, then I can understand doing it. But if you have a list of 100 aliases for a physical interface, they really should all be done ... or at least attempted ... at once, and do any triggers needed after that.
So, how can I configure or modify Ubuntu Server 9.10 to do that?
I have each alias listed in the "/etc/network/interfaces" file with a separate "auto" and "iface" section for each one, with sequential sub-interface numbers appended to the interface name. I tried it without those sections (e.g. just "address" and other items in sequence) and that prevents the system from even coming up (bootable CD to the rescue to undo that). At least cntrl-alt-del did reboot it.
I tried to attach the /etc/network/interfaces file, but I don't know if it worked because I see no confirmations about it. if it didn't attach and you need to see it, say so, and I'll just paste it in a followup.
Like the title stated Anyone with experience or suggestion, please do share. I've tinkered all night with this thing. Never get the VBox service I created to start.Here is my final code before I dried my brain.
Code:
# Archayl Server startup
#
[code]....
I recently discovered upstart is launching sshd on my machine even though I disabled it with `sudo update-rc.d -f ssh remove`. I tried to find a way to prevent upstart from launching ssh by default, but the best I can think of is removing /etc/init/ssh.conf (I just uninstalled openssh-server).I'd like to disable it without doing this, though. This would make it easier to enable sshd when I need it
View 8 Replies View RelatedFrom what I've read, it appears that the respawn stanza in /etc/init/mysql.conf would give me the restart option if the daemon crashes, but I want to make sure other safety features of mysqld_safe are present as well.My /etc/init/mysql.conf is the original. I've tried changing the exec stanza from /usr/sbin/mysqld to /usr/sbin/mysqld_safe but the job fails when I sudo service mysql start.mysql.conf
Code:
# MySQL Service
description "MySQL Server"
[code]....
How i do create autostart script for UpStart ?
I want autostart this commands with UpStart:
mkdir /home/user/_1_
mkdir /_1_
I had read that squeeze was to use upstart instead of sysvinit. Anyway, in playing with splashy, I decided to install upstart to see if it would work, which it does just fine. When I check for updates in synaptic, it always wants to remove upstart in favour of sysvinit. I wouldn't have a problem with that except, with sysvinit, squeeze no longer shuts down or starts up.
View 3 Replies View RelatedWhere can I find a list of services converted to upstart in Ubuntu 10.04? What is the syntax for stopping, starting and restarting these services?
View 6 Replies View Relatedwhy upstart is broken in 10.04? The old init of /etc/init.d/mythtv-backend start worked fine in 9.10.
$ start mythtv-backend
start: Rejected send message, 1 matched rules; type="method_call", sender=":1.93" (uid=1000 pid=21758 comm="start) interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply=0 destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init"))
mysqld not running on boot, I can start it manually with
Code:
sudo -u mysql mysqld
If I attempt to start it with Upstart I get
Code:
dom@mythbox:~$ sudo start mysql
start: Job failed to start
I'd like to reconfigure vsftpd so that it does not start on boot (and I can enable/disable it using service vsftpd start/stop).
Though I've seen posts in the forums that stated that upstart jobs can be disabled by moving the /etc/init/job.conf file, other sites commented that the original file will be recreated on updates.
The other two suggestions were to alter the upstart script such that either the process starts on never:
Code:
start on (never
and filesystem
and net-device-up IFACE!=lo)
stop on runlevel [!2345]
[Code]....
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.
View 5 Replies View RelatedI'd like to create a couple of upstart scripts for some network service daemons (eg. usenet downloading service, torrent service, media management services, etc).Basically they should start after the network service is started and the system is running (runlevel 2?) but I'm just wondering if anybody has an example script or more specific start/stop conditions that I can use.
View 1 Replies View RelatedI have posted this somewhere here before and solved it but can't seem to find it. Just waisted 50 minutes googling and checking man pages for upstart. By the way; are man pages written by someone using their tows to type and getting beaten by a stick for every character they type? It seems missing a lot of info. Anyway, I know smbd is started with /etc/init/smbd.conf and there is a line like:
Code: start on local-filesystems Now it needs to be started on? (manually) I can't seem to find any useful information but did seem to find the upstart man pages a hundred times or so (same info same missing parts). I would love to get involved writing documentation for these things if only I know what I was doing.
I installed MySQL and Apache2 to develop & test out the site I'm writing. However since I'll be using them purely for internal use (not exposed to the Net), I don't want them to start with every boot-up, but would like to start them manually when I desire, and stop them after use.With previous Ubuntu (Jaunty) I'd used chkconfig to configure services, but since the current version (Maverick) uses Upstart, is chkconfig still applicable?
I also installed 'bum' (Boot-Up Manager), but strangely, it displays the MySQL server as "unchecked" even though it's running (and starts at boot-up), so I cant see how I can prevent it from starting at boot-up through bum. chkconfig also displays MySQL as not active at runlevel 5, when in fact, it is.
I'd like to know what's the recommended (official) way to configure boot-up services with the Upstart system? I don't suppose directly editing the *.conf files in /etc/init is the best (or even correct) way?
On Maverick + up-to-date on updates on Mini ITX (Asus AT3N7A-I) I have a Perl script that I want to run continually to extract values from XML that appears on a USB port every 5 seconds and stuff the extracted values into an RR Database (RRD). I have created an Upstart job, called currentCost.conf (permissions=644 owner=root): #readCurrentCostData4RRD.pl daemon
description "regular background program processing daemon"
start on runlevel [5]
stop on runlevel [!5]
expect fork
respawn
exec perl /home/greg/currentCost/readCurrentCostData4RRD.pl > /tmp/RCCD4RRD.out 2>&1
[Code]...
Not sure if this is the correct area to ask this question as it pertains to Upstart but not necessarily to Ubuntu.
Anyhoo, I have made a small alteration (obviously the cause of error ) but not really sure why it does not work.
rsyslog.conf:
Code:
# rsyslog - system logging daemon
#
# rsyslog is an enhanced multi-threaded replacement for the traditional
# syslog daemon, logging messages from applications
[Code].....
What is the correct way to stop upstart services from staring at boot time ? I'm doing something like this example in /etc/init/mysql.conf:
Code:
#start on (net-device-up
# and local-filesystems
# and runlevel [2345])
start on runlevel [!0123456] # I ADDED THIS LINE (and commented the above ones)
stop on runlevel [016]
1. Is this the correct way ?
2. Is there no way of doing something like we do with update-rc.d -f apache2 remove ?
3. When will ubuntu ship a gui to add or remove services from boot ?
now everytime I restart my maveric box I have to
Code:
root@tux:~# start smbd
smbd start/running, process 16067
root@tux:~#
oh and stop firestarter. Ok the firewall issue, is probably simple. I am more concerned that an upstart task won't start. I have checked in boot-up manager, and it is asked to start. This was an upgrade from Lucid, where I hadno problems.