Network services don't start automatically at boot time

On a fresh install, no OpenVPN configuration is installed, so at boot OpenVPN would return

 * Starting virtual private network daemon(s)...
 * No VPN is running.

Obviously, on upgrade from jaunty, if you have configurations defined in /etc/openvpn, those would get started.

Could you give more information on the contents of /etc/openvpn on your failing "fresh beta install" and on the working "upgrade from jaunty" ?

I'm using the same configuration and the vpn is started successfully if I start it using /etc/init.d/openvpn start in both cases.

I guess something is up with the init.d->upstart transition but I'm not sure.

Are you using the same /etc/default/openvpn settings ?
Anything in the logs that would explain it ? Wha

(grmbl) What does it display on boot, if anything ? Thanks in advance.

Can't reproduce... although on karmic the boot message is much less informative, it still seems to start VPN configs alright. Please include /var/log/syslog for more information.

Could this bug be related to bug 449323? Do these two bugs happen on the same system? Is the network configured correctly and brought up?

@Mathias Gug
Yes that's on the same system. I will post the requested informations as soon as I get a hand on this machine again. Networking works (after login as it's using wireless/Network Manager to connect).

If you use NetworkManager to handle your network settings, the network services that start at boot will certainly fail... since network will only be available fater you log in. How do you handle your networking on the jaunty->karmic upgraded machine ? Are you using "system settings" in NetworkManager ?

@Thierry Carrez
Nope this is not checked. But I can tell you that I have more than 50 jaunty users where I only apt-get install openssh-server and openvpn where most of those users are using laptops and Network Manager in its default configuration and both ssh server and vpn client handle the fact that the network is brought up later fine.

I'll be able to send the requested files tomorrow I think

I did an install from daily CD and couldn't reproduce this.
OpenVPN starts and logs "Network is unreachable" until the network interface comes up. Then it connects alright.

I have exactly the same problem, from upgrading jaunty to karmic, openvpn doesn't start automatically, let me know wich files you need to find the problem

@small_frenchy,
I found out that openssh, openvpn and cups don't start automatically on this machine, do cups start on your system (or ssh if you have it installed) ?

Obviously not specific to openvpn, so reassigning... Tentatively assigned to upstart, but still incomplete.

@Jonathan Ernst,
In my case, openssh and cups starts without any problem.

@small_frenchy: then your bug isn't the same issue. Please open a separate bug against openvpn.

The bug has been fixed after the last updates on the affected machine... (ssh, openvpn and cups start now)

upstart should only receive bugs if you can prove they are with the init daemon, remember that just like in sysvinit, it's other packages that ship the configuration files - please don't use it as a dumping ground

though original reporter says this is now fixed

I'm still experiencing this problem on 9.10 with all updates installed.

before I can connect to VPN through the nm-applet I have to manually run:

#sudo /etc/init.d/openvpn start

#sudo openvpn -C myvpn.conf connects me too.

So I don't know to what it's related, but I read on the unbuntu forums it could be fixed with a change to the openvpninitscript by addding a 'sleep 3' timout somewhere.

http://ubuntuforums.org/showpost.php?p=63967&postcount=6

hope this helps

KaOS-bEat: looks like a separate issue, could you open a separate bug ?

I have same issue in 10.04. Openvpn server doesn't start automatically on system boot, but it starts when I run 'sudo /etc/init.d/openvpn start'. Looks like there is no configuration file for the new upstart daemon in the package.
This command doesn't wotk:
$ sudo start openvpn
start: Unknown job: openvpn

DistroRelease: Ubuntu 10.04
Package: openvpn 2.1.0-1ubuntu1
PackageArchitecture: amd64
ProblemType: Bug
ProcEnviron:
  PATH=(custom, user)
  LANG=ru_RU.UTF-8
  SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
SourcePackage: openvpn
Tags: lucid
Uname: Linux 2.6.32-22-generic x86_64

Nevermind, for some reason it starts now...

Sorry but I have the same issue in a fresh installation on Ubuntu Server 10.04. On server boot openvpn autostart fail, but after the login when I run "/etc/init.d/openvpn start" it start normally. In the /var/log/syslog it says that it can't assign the ip address to the server. Is it possible that the tap interface isn't ready when openvpn start?