Hide Forgot
Description of problem: My machine was hosed (GDM shows a window full of boxes, and I can't log into Gnome), so I booted into runlevel 1. But there is a longish wait while the (non-networked!) machine asks for current time and date via NTP, and then hangs waiting for NTP service. The only way out was to boot into runlevel 3. Version-Release number of selected component (if applicable): systemd-17-2.fc15.x86_64 How reproducible: Always. Tried several kernels here. Steps to Reproduce: 1. Boot into runlevel 1 2. 3. Actual results: Long timeouts, finally hang Expected results: Speedy boot into maintenance mode. Additional info:
Hmm, can you paste "systemctl show ntpd.service"? Not sure what might have pulled in NTP into runlevel 1 for you.
Now I've got systemd-17-6.fc16.x86_64. This machine started as Fedora 13 (around the time it came out) and went to rawhide almost immediately. $ systemctl show ntpd.service Id=ntpd.service Names=ntpd.service Requires=basic.target WantedBy=multi-user.target Conflicts=shutdown.target Before=single.service smb.service nmb.service shutdown.target multi-user.target smolt.service After=syslog.target ntpdate.service dnsmasq.service basic.target auditd.service netconsole.service qemu.service Description=Network Time Service LoadState=loaded ActiveState=active SubState=running FragmentPath=/lib/systemd/system/ntpd.service InactiveExitTimestamp=Wed, 16 Feb 2011 10:54:09 -0300 ActiveEnterTimestamp=Wed, 16 Feb 2011 10:54:09 -0300 CanStart=yes CanStop=yes CanReload=no CanIsolate=no StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes DefaultControlGroup=name=systemd:/system/ntpd.service ControlGroups=cpu:/system/ntpd.service name=systemd:/system/ntpd.service NeedDaemonReload=no JobTimeoutUSec=0 Type=simple Restart=no NotifyAccess=none RestartUSec=100ms TimeoutUSec=1min ExecStart={ path=/usr/sbin/ntpd ; argv[]=/usr/sbin/ntpd -n -u ntp:ntp $OPTIONS ; ignore=no ; start_time=[Wed, 16 Feb 2011 10:54:09 -0300] ; stop_time=[n/a] ; pid=1400 ; code=(null) ; status=0/ } Environment=OPTIONS=-g UMask=0002 LimitCPU=18446744073709551615 LimitFSIZE=18446744073709551615 LimitDATA=18446744073709551615 LimitSTACK=18446744073709551615 LimitCORE=18446744073709551615 LimitRSS=18446744073709551615 LimitNOFILE=1024 LimitAS=18446744073709551615 LimitNPROC=30485 LimitMEMLOCK=65536 LimitLOCKS=18446744073709551615 LimitSIGPENDING=30485 LimitMSGQUEUE=819200 LimitNICE=0 LimitRTPRIO=0 LimitRTTIME=18446744073709551615 OOMScoreAdjust=0 Nice=0 IOScheduling=0 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 TimerSlackNSec=50000 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardOutput=inherit StandardError=inherit SyslogPriority=30 SyslogLevelPrefix=yes SecureBits=0 CapabilityBoundingSetDrop=0 MountFlags=1048576 PrivateTmp=no SameProcessGroup=no KillMode=control-group KillSignal=15 PermissionsStartOnly=no RootDirectoryStartOnly=no RemainAfterExit=no ExecMainStartTimestamp=Wed, 16 Feb 2011 10:54:09 -0300 ExecMainExitTimestamp=Wed, 16 Feb 2011 10:54:09 -0300 ExecMainPID=1400 ExecMainCode=0 ExecMainStatus=0 MainPID=1400 ControlPID=0 SysVStartPriority=58 FsckPassNo=0
BTW, I was checking something on the machine in runlevel 5 without any network connection lately, and on shutting down I again saw that NTP date had failed (obvious), and the NTP daemon had been started.
I tried runlevel 1 again, no NTP shenanigans now. But it still tries to run NTP date and the NTP daemon in runlevel 3 if there is no network.
Hmm, so what is precisely the issue now? What are you not expecting that happens and what are you expecting that does not happen?
Just tried again on this netbook, configured to run NetworkManager (and thus having network) only when a user logs in. The NTP service is started (and fails due to no DNS, obvious) _before_ anybody logs in (i.e., before any network is available). I'd want NTP (and other network-dependent services) get started only when the network is available.
On current F15, if you run "systemctl enable NetworkManager-wait-online.service", do things work then?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Closing this bug since the needinfo request has not been responded to in several months.