[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
@nacc: Yes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
@nacc: The system was originally installed with Ubuntu Server 14.04. It has been upgraded to 16.04. apt policy open-iscsi: open-iscsi: Installed: 2.0.873+git0.3b4b4500-14ubuntu3.3 Candidate: 2.0.873+git0.3b4b4500-14ubuntu3.3 Version table: *** 2.0.873+git0.3b4b4500-14ubuntu3.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0.873+git0.3b4b4500-14ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 2.0.873-3ubuntu13 500 500 http://us.archive.ubuntu.com/ubuntu wily/main amd64 Packages Modifying those two lines in /lib/systemd/system/open-iscsi.service does not have any effect - I'm still running into the timeout. I have attached a new journal.txt (per instructions in #8). This time, the error message is logout-all.sh[2206]: iscsiadm: No matching sessions found ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+attachment/4894804/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
@nacc: No, my lines do not like that. On my xenial system, I have: Wants=network-online.target remote-fs-pre.target After=network-online.target Which is probably why on my system the iscsid daemon shuts down before the logout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
@nacc: Add-on: On my Debian systems (Debian jessie and stretch) that also experience this issue, however, the lines do look like what you described - and still the system hangs at reboot / shutdown. In a previous message it sounded like you had identified an issue and a fix - did I misinterpret your response? If so, was it a fix I can apply to my xenial system and test? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
I've installed a system with the daily artful server image, and the error is not present for me. However, I'm not sure how useful that test is, given that I didn't experience the error during a fresh install of xenial. I've attached the journal from the artful install, and it looks to me like the steps are now in the right order. Was adding "iscsid.service" to the "after" and "wants" lines in /lib/systemd/system/open- iscsi.service the only change that was required? If so, I'd be happy to test that on my server that's experiencing the issue... ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+attachment/4892287/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
Thanks, @nacc. So, here's what I've done in the meantime: - I've built another server with 14.04. Clean install, only OpenSSH server. Connected to an iscsi target. Reboot works. - Upgraded the server to 16.04.02. Reboot still works. Guess my hunch was wrong. :( - I've attached the journal as requested. You'll see that the iscsid daemon shuts down before the "logout-all.sh" script runs. Since iscsid has shut down, that script does not run successfully. My machines that exhibit the problem use an iSCSI drive for: - mythbackend (storage for recorded videos - that's the Ubuntu journal attached) - postgres and mysql storage (Debian server) - nginx storage (also on Debian) Thanks for your help. ** Attachment added: "Requested journal file" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+attachment/4891508/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
@nacc: I can certainly do that - but it won't be quite as fast as my response yesterday, as the machine that exhibits this error is in use during the day, and I need to schedule the downtime. In the meantime, I have installed a test machine from scratch, using the standard Ubuntu LTS server ISO. All I did on that machine was to set a static IP address, upgraded to the latest packages, and configured an open-iscsi mount. Lo and behold, the test machine does not exhibit the error. My machine that does exhibit the error was upgraded using 'do-release-upgrade' from the previous LTS version (14.04). My Debian machines similarly were upgraded from wheezy to jessie (which introduced the issue with the switch to systemd). So, for now, I would say there's something different between upgrade and fresh install that causes this. I will find some time today for the downtime of my other machine and attach the persistent journal info as requested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
I checked my system (16.04.02) which is also exhibiting this issue (my Debian systems do as well). On both OS, the open-iscsi service is in "active (exited)" state after booting (and not in failed state): ● open-iscsi.service - Login to default iSCSI targets Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor preset: enabled) Active: active (exited) since Sat 2017-06-03 06:00:19 PDT; 3 days ago Docs: man:iscsiadm(8) man:iscsid(8) Process: 978 ExecStart=/lib/open-iscsi/activate-storage.sh (code=exited, status=0/SUCCESS) Process: 918 ExecStart=/sbin/iscsiadm -m node --loginall=automatic (code=exited, status=0/SUCCESS) Process: 905 ExecStartPre=/bin/systemctl --quiet is-active iscsid.service (code=exited, status=0/SUCCESS) Main PID: 978 (code=exited, status=0/SUCCESS) CGroup: /system.slice/open-iscsi.service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189163] [NEW] Emacs won't start after update to raring
Public bug reported: Similarly to eboard (see bug #1174381), emacs will not start after upgrading Kubuntu to version 13.04. The symptoms are the same - the process runs, but now window appears on the screen. When starting in the shell, no output is produced. Ctrl-C will terminate emacs when started in the shell ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs (not installed) ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Sun Jun 9 07:53:01 2013 InstallationDate: Installed on 2011-12-04 (553 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: emacs-defaults UpgradeStatus: Upgraded to raring on 2013-04-26 (43 days ago) ** Affects: emacs-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189163 Title: Emacs won't start after update to raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs-defaults/+bug/1189163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178706] Re: System freeze after DPMS off with external monitors
Thanks for the suggestion - that seems to have fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178706 Title: System freeze after DPMS off with external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1178706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178706] [NEW] Power Management causes system to be unusable
Public bug reported: I'm using Kubuntu 13.04. Since the upgrade, I can't use the power management features related to the monitor on my laptop when using external monitors. Once the screen is blacked for power management, I can't bring it back to life. Neither keyboard nor mouse show any reaction, and I also cannot login remotely anymore. This does not happen when I'm using just the laptop screen. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin Date: Fri May 10 07:41:35 2013 DistUpgraded: 2013-04-26 09:10:09,769 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: kubuntu DkmsStatus: tp-smapi, 0.41, 3.8.0-19-generic, x86_64: installed vboxhost, 4.2.12, 3.8.0-19-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2011-12-04 (523 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus ** (process:2529): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory static bool QDeclarativeMetaType::isModule(const QByteArray&, int, int) Qt 4.7 import detected; please note that Qt 4.7 is directly reusable as QtQuick 1.x with no code changes. Continuing, but startup time will be slower. LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus ** (process:2527): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory static bool QDeclarativeMetaType::isModule(const QByteArray&, int, int) Qt 4.7 import detected; please note that Qt 4.7 is directly reusable as QtQuick 1.x with no code changes. Continuing, but startup time will be slower. MachineType: LENOVO 4286CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=fe42e798-27b2-49c8-843b-afb45b93c29b ro quiet splash i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 pcie_aspm=force vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to raring on 2013-04-26 (13 days ago) dmi.bios.date: 10/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET54WW (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET54WW(1.24):bd10/18/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Fri May 10 07:31:54 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178706 Title: Power Management causes system to be unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174381] [NEW] Eboard won't start after upgrade to Kubuntu 13.04
Public bug reported: After a recent upgrade to Kubuntu 13.04, eboard will no longer start. When starting in a shell, no output is produced. When hitting Ctrl-C once in the shell, I get the following: Gtk-CRITICAL **: IA__gtk_main_quit: assertion `main_loops != NULL' failed Hitting Ctrl-C again will kill eboard. Running eboard -debug does not produce the DEBUG.eboard file mentioned in the man page. Running 'strace eboard' produces the output in the attached file. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: eboard 1.1.1-5ubuntu1 [modified: usr/share/doc/eboard/README.gz] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon Apr 29 08:48:05 2013 ExecutablePath: /usr/games/eboard InstallationDate: Installed on 2011-12-04 (512 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: eboard UpgradeStatus: Upgraded to raring on 2013-04-26 (2 days ago) ** Affects: eboard (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ** Attachment added: "eboard.strace" https://bugs.launchpad.net/bugs/1174381/+attachment/3659061/+files/eboard.strace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174381 Title: Eboard won't start after upgrade to Kubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eboard/+bug/1174381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
