Debian Configuration :: Systemd Boot Is Now Verbose

Aug 13, 2015

When I first started running Jessie 8.1 I noticed that after the disk check the boot was quiet, ie. no messages to the terminal . However, something has happened and now when I boot the machine I get a verbose listing of all the processes being started. Is there a way to change it back to the way it was? In other words a quiet boot. The only thing I know of that has been 'anomalous' behavior is the other day when doing a mp4 to avi conversion, using avconv, I apparently had an over temp condition which closed my LXDE session and brought me to the login prompt. Don't know what other info one may need but feel free to ask for more, if necessary.

View 13 Replies


ADVERTISEMENT

Debian Configuration :: Systemd Can't Read Boot Logs Of Failed Boots

Mar 25, 2016

I'm getting BSOD when I'm booting my main system (debian 8 fully updated). I get a BSOD with a _ sign. URL...because I can't access to failed boots files. Besides having the files

Code: Select allfelipe@debian ~ % ls /var/log/journal   
362d07f9e18b45f8aec4575c347f181d  92e8a448f7a348719da129184a7e6821

Code: Select allfelipe@debian ~ % journalctl --list-boots
 0 0c51ae5b67f144059c5470dbe345d621 vie 2016-03-25 09:05:29 ART—vie 2016-03-25 09:11:58 ART

View 3 Replies View Related

Debian Configuration :: Wheezy - After Update Systemd Turn Off Laptop Screen On Boot

Sep 25, 2015

I decided to update all the software on my computer. Fortunately, it upgraded kernel version 3.14 to 3.16. I was happy to learn that suspend now worked on my laptop by calling pm-suspend, but it did not worked by closing the lid. So I search and found on debian's website that installing systemd and adding some config lines in /etc/systemd/logind.conf would sove the issue. So I followed the procedure and did like instructed, to end up with a computer that boots on black screen.

The last verbrose line I see on boot up is "kvm disabled by bios" and then it shutdown down the screen. The computer works, as I can login and shutdown by doing those operation blindly.

I tried removing systemd but it still does not work. If I use the old kernel 3.14 I can boot without any problem, but if I use kernel 3.16, I boot to a black screen. I remember successfully booting in 3.16 before installing systemd.

View 4 Replies View Related

Debian Configuration :: Systemd Custom Service

Aug 4, 2015

On macbook air 6.2, i've installed a Debian jessie mate DE, dual boot using refind. I'm currently fine-tuning it. I've made a script following powertop advice:

Code: Select all[newb@debian /etc/systemd/system]$ cat mba_kb_sp.sh
#!/bin/sh
echo 'auto' > '/sys/bus/usb/devices/1-3.1/power/control';
echo 'auto' > '/sys/bus/usb/devices/1-3.2/power/control';
echo 'auto' > '/sys/bus/usb/devices/1-5/power/control';
exit 0

[Code] ....

All seems to work fine, however when i check the sys file it didn't change. But I can start manually the systemd service and, this time, it works.

View 2 Replies View Related

Debian Configuration :: Installing Libpam-systemd

Aug 12, 2015

I upgraded my machine from Wheezy to Jessie, opted to not install systemd yet. When i try to upgrade kde-plasma-desktop, apt doesn't let me do it.

For some reason "libpam-systemd : Depends: systemd (= 215-17+deb8u1) but it is not installable"

Installing systemd-shim doesn't work. Libpam-systemd package site gives impression that you would be able to use systemd or systemd-shim.

Tried looking through changelog, but it didn't really give any hint.

At 215-6 there are just
Code: Select allSwitch libpam-systemd dependencies to prefer systemd-shim over
    systemd-sysv, to implement the CTTE decision #746578. This is a no-op on
    systems which already have systemd-sysv installed, but will prevent
    installing that on upgrades. (Closes: #769747)
Version of libpam-systemd that would be installed is "Candidate: 215-17+deb8u1"

View 2 Replies View Related

Debian Configuration :: Systemd - NTP Host Name Not Found

Apr 14, 2016

my system keeps on telling me about an error:

Code: Select allsudo journalctl  -p 0..3
Apr 14 10:36:11 debian ntpd_intres[682]: host name not found: ptbtime1.ptb.de
Apr 14 10:36:11 debian ntpd_intres[682]: host name not found: ptbtime2.ptb.de
Apr 14 10:36:11 debian ntpd_intres[682]: host name not found: ptbtime3.ptb.de

A quick check

Code: Select allsystemctl status ntp.service
ntp.service - LSB: Start NTP daemon
   Loaded: loaded (/etc/init.d/ntp)
   
[code]...

3 packets transmitted, 0 received, 100% packet loss, time 1999ms.Same result when using the standard Debian ntp time servers like "server 0.debian.pool.ntp.org iburst" in /etc/ntp.conf.

View 13 Replies View Related

Debian Configuration :: Enabling Persistent Logs With Systemd

Dec 1, 2015

How to enable persistent logging with systemd? I find it really weird that all this machinery that is systemd doesn't store persistent logs, what if I'm trying to retrieve some information regarding previous boots?

For instance: I have random suspend issues, after rebooting the computer there's no trace left in the logs of what happened, and furthermore (at least in Jessie) I can no longer see a pm-suspend log.

So, at first it sounds like all you have to do is edit journald.conf setting #Storage=auto to "persistent" and create the /var/log/journal directory, but then reading here /usr/share/doc/systemd/README.Debian

Code: Select allEnabling persistent logging in journald
=======================================

To enable persistent logging, create /var/log/journal and set up proper permissions:

install -d -g systemd-journal /var/log/journal
setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal

and here [URL] ....

There are two main reasons why I decided to not enable persistent logging just yet ....

We did get corrupt journal files in the past where the journal then no longer worked at all [1]. With volatile you can just reboot and have a clean state again. Admittedly, the journal has seen a lot of improvements in the mean time and hopefully is more robust, so this point is no longer true.

We still install rsyslog by default. That means we get store them twice. This is something we don't want to do atm.

View 3 Replies View Related

Debian Configuration :: Udev / Systemd Change Some Rules In 8.0

Apr 18, 2016

I have SSD drives without SCT support, because of this I want to tune /sys/block/device-name/device/timeout in order to force mdadm put these drives offline. So, I can see my drive like this:

/dev/disk/by-id/ata-OCZ-SABER1000_A22MJ061512000074.

Where can I tune /sys/block/device-name/device/timeout from 30 to 7 sec only for these drive? I don't want to use rc.local.

Can I create right udev rules for it in /etc/udev/rules.d?

I want to avoid any conflict with /lib/udev/rules.d.

Code: Select all# udevadm monitor --environment --udev
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

UDEV  [9302.549485] add      /devices/pci0000:00/0000:00:01.2/0000:03:00.0/host0/target0:0:0 (scsi)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:01.2/0000:03:00.0/host0/target0:0:0
DEVTYPE=scsi_target
SEQNUM=5210
SUBSYSTEM=scsi

[Code] ....

View 0 Replies View Related

Debian Configuration :: Systemd Automounts For Removable Media Not Timing Out

Jul 18, 2015

I have the following hardware setup:

a NAS running Debian that frequently (but not always) has two removable media attached,a Debian desktop that mounts the above NAS via sshfs,the aforementioned removable media are symlinked to the directory on tha NAS that is then mounted by the desktop.

What I'd like this setup to do is to immediately time out if mounts as unavailable. Instead, I only get the expected behaviour if the NAS is down (the ssh client takes about 3 seconds to do that); if it's up, the removable media automounts (they are symlinked to the directory shared with the desktop) seem to never time out, ever. This happens locally on the NAS as well, when ssh'ing to the NAS and trying to run `ls /media/Storage` or `ls /media/Backup`, these commands never return. It's as if systemd was ignoring the x-systemd.device-timeout setting on the NAS.

The relevant part of the NAS's fstab:

Code: Select all/dev/sdb1       /media/Backup   ext4    defaults,noauto,x-systemd.automount,x-systemd.device-timeout=1s,rw,user,nofail,x-systemd.idle-timeout=30s       0       1
/dev/sdc1       /media/Storage  ext4    defaults,noauto,x-systemd.automount,x-systemd.device-timeout=1s,rw,exec,nofail,x-systemd.idle-timeout=5min      0       1

[Code] ....

I find it highly interesting that despite both removable media being detached, only one is flagged as having a dependency failed. Both paths exhibit the hang behaviour, though.

What can I do to actually time out when the media are not there?

View 4 Replies View Related

Debian Configuration :: Systemd Fails To Raise Up Network Interface

Mar 15, 2016

Is this a problem of systemd or network-manager however when I started to see this alert I noticed the nm-applet doesn't start automatically anymore.

Code: Select allsystemctl status network
networking.service       network-online.target    network.target
network-manager.service  network-pre.target       
zagor@Debian-635:~$ systemctl status networking.service
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor prese

[Code] ....

View 5 Replies View Related

Debian Configuration :: Corrupted (permanent) Systemd Logs In Jessie

Apr 22, 2016

I've enabled permanent systemd logs in Jessie, and after a while I'm seeing messages about corrupted logs when checking with journalctl --verify

Code: Select allInvalid tail monotonic timestamp 0%
File corruption detected at /var/log/journal/..........

as far as I can see, there is currently no option to delete this files from within systemd facilities, is that correct?

Should they be deleted manually, or just left alone?

Apparently I can still read all older logs regardless of such reported corruption, using the journalctl --boot -n option.

EDIT:Another thing coming to mind is that this has been happening for me not only in Jessie but in every systemd-based distro that I've tried, once permanent logging is enabled: is that some kind of systemd bug?

What would exactly mean

Code: Select allFile corruption detected at /var/log/journal/38d5e6b861134eadb37cbd64b98a66bd/user-65534@d1745ac610d2459f940a24f27abd6d47-0000000000000f14-00051b8d2dabdcac.journal:000000 (of 8388608 bytes, 0%)

in particular, the 0% of 8388608 bytes part ?

View 0 Replies View Related

Debian Configuration :: Plex Media Server Startup Script Due To Systemd

May 6, 2015

My plex media server does not work with systemd apparently but running the command below makes plex startup properly

Code: Select all/usr/sbin/start_pms &

Is there anyway to make this command run on my computer at startup.

I am running debian 8 jessie.

View 4 Replies View Related

Debian Configuration :: Hardware Event Listening Scripts With Systemd Not Acpid

Aug 22, 2015

Just migrated to stretch, and noticed we're not using acpid anymore. Had couple of scripts at /etc/acpi/events listening for some events. What would be the alternative with systemd?

View 2 Replies View Related

Ubuntu :: Save The Verbose Boot Process?

Jun 6, 2010

Fighting against Grub2 boot troubles, i've seen on screen that the problems comes when detecting internal SATA devices.

But logs dont help about the scanning boot process, so i search a way to log this verbose process by adding some code into /etc/default/grub or something else.

View 6 Replies View Related

Ubuntu :: Make Verbose Boot The Default?

Sep 28, 2010

My laptop's ubuntu partition has been a bit sluggish to boot lately, and I'd like to swap to a verbose boot so I can see if there are any processes I can eliminate to improve speed. E.g. my slackware install was waiting for an 8 second timeout initially, but I was able to stop it.

View 7 Replies View Related

Debian Configuration :: Boot Via PXE, "no Default Or Ui Configuration Directive?

Mar 19, 2011

A week ago I opened this thread viewtopic.php?f=17&t=61580 in "Board index ‹ Help ‹ Installation" and asked for a moderator to move this to here. Because it hasnt happened up to know, I am reopening the thread here. It would be reeeeally great if somebody could help me with my problem!

I own two computers, one netbook and one laptop. I want to boot my netbook as a diskless client via PXE.I set up a dhcp-, tftp and nfs-server on my laptop but when i boot my netbook, the follwoing messages are displayed:(to make it more clear, i uploaded the whole output and shortened the output below)

[Code]...

View 1 Replies View Related

Fedora :: Systemd Boot Script - Alternative Desktop To Gnome3

May 30, 2011

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).

View 4 Replies View Related

Debian :: Computer Closes Down Unexpectedly - SystemD?

May 21, 2015

I leave my system in suspend mode overnight and wake it up first thing in the morning. At 9:15 it will automatically run housekeeping scripts via cron and these are completed by 9:30. Some time later I will turn on the monitor and start work. Since moving from Wheezy to Jessie the system has switched off for no apparent reason. I checked the syslog and auth.log and found it completed all it's tasks at 9:30 then started shutting down at 9:35. Relevant extracts from these logs are attached ...

My OS is Jessie 64 bit with Cinnamon on a quite standard Gigabyte desktop with dual core intel processor, 4Gb RAM and SSD drive. It uses NVidia drivers and there were no unusual entries in x.org.log.

AUTH LOG
May 21 09:36:15 michael systemd-logind[685]: System is powering down.
May 21 09:36:15 michael gnome-keyring-daemon[1477]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
May 21 09:36:15 michael lightdm: pam_unix(lightdm:session): session closed for user michael
May 21 09:36:16 michael polkitd(authority=local): Unregistered Authentication Agent for unix-session:1 (system bus name :1.39, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_AU.UTF-8) (disconnected from bus)
May 21 09:36:16 michael sshd[680]: Received signal 15; terminating.

[Code] .....

View 1 Replies View Related

Debian :: 8.1 - Can't Process Updates For Udev And Systemd

Jun 6, 2015

I was trying to install recent updates, but apt-get couldn't do this. Here's the output I got:

Code: Select all(Reading database ... 187979 files and directories currently installed.)
Preparing to unpack .../udev_215-17+deb8u1_i386.deb ...
Failed to execute operation: Connection reset by peer

Message from syslogd@debian-LAPTOP at Jun  6 14:56:49 ...
kernel:[357720.299647] systemd[1]: segfault at b87cf92c ip b765e480 sp bf872e60 error 4 in systemd[b762f000+130000]
Unpacking udev (215-17+deb8u1) over (215-17) ...
Failed to execute operation: Activation of org.freedesktop.systemd1 timed out

[Code] ....

Now I can't continue upgrading because every time it tries to finish the previous update and fails to process udev.

I don't know if it's relevant, but while upgrading udev for the first time, my laptop switched to tty1 on its own. When I switched it back to graphic subsystem, it still was in process of upgrading udev or systemd and after all failed to finish.

View 3 Replies View Related

Debian :: Systemd / Sshd And Login To Localhost

Sep 20, 2015

When i login on localhost with pubkey-auth, i get the following in my log

Code: Select allSep 20 12:42:27 aldebaran sshd[19745]: Accepted publickey for root from 127.0.0.1 port 37520 ssh2: RSA 45:4e:27:4d:30:f5:3d:25:10:d0:92:88:53:77:1a:3b
Sep 20 12:42:27 aldebaran sshd[19745]: pam_unix(sshd:session): session opened for user root by (uid=0)
Sep 20 12:42:27 aldebaran systemd[19757]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Sep 20 12:42:27 aldebaran systemd-logind[585]: New session 70 of user root.
Sep 20 12:42:27 aldebaran systemd[19757]: Starting Paths.

[code]....

View 1 Replies View Related

Debian :: Breaking Ordering Cycle (systemd)

Nov 8, 2015

When I boot my debian desktop, I get these errors:

Code: Select allnov 08 22:05:12 Luca-PC systemd[1]: Job paths.target/start deleted to break ordering cycle starting with basic.target/start
nov 08 22:05:12 Luca-PC systemd[1]: Job rpcbind.service/start deleted to break ordering cycle starting with basic.target/start
nov 08 22:05:15 Luca-PC systemd[1]: Job paths.target/start deleted to break ordering cycle starting with basic.target/start
nov 08 22:05:15 Luca-PC systemd[1]: Job sysinit.target/start deleted to break ordering cycle starting with basic.target/start
nov 08 22:05:15 Luca-PC systemd[1]: Job rpcbind.service/start deleted to break ordering cycle starting with sysinit.target/start

The system works perfectly, but I'd like to understand why I get these errors, and how I can fix them.

View 4 Replies View Related

Debian :: How To Log (Remaining Processes) Of Systemd-shutdown

Mar 22, 2016

How to log "remaining processes"? How to know their names?

Code: Select allsystemd-shutdown[1]: Sending SIGTERM to remaining processes...

View 4 Replies View Related

Debian :: How To Log Bootup And Shutdown Messages (with Systemd)

Jun 23, 2015

During the boot-sequence of jessie there is more text flying by on the screen (including some errors or warnings) than I can read thorugh fast enough. I don't think this is very serious stuff, and if it were I could always look at dmesg and or syslog i /var/log but I would find it really convenient to log these messages in a file instead of sifting through or grep-ing dmesg.

When duckduckgoing this matter I found [URL] ....

I installed tried bootlogd but when configuring it to "yes" and rebooting nothing comes up in /var/log/boot.

Then I saw this line in above link

If you use systemd as your init system, you may need to use systemctl to debug boot problems.

View 11 Replies View Related

Debian :: Start Script Via Systemd - Error

Apr 27, 2016

I tried to set up my linux server with a specific script that can control my gameserver (mta). The thing is, I wanted to let this script be forced to start by the systemd, so I created a service called 'mtadef' (btw: same name as the user).

Here is the service script:

Code: Select all[Unit]
Description="MTA: Primary Server"

[Service]
Type=Forking
User=mtadef
ExecStart=/home/mtadef/mtastart.sh
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

And here is my shellscript (mtastart.sh):

Code: Select all#!/bin/sh
if [ $# -ne 1 ]
   then
      screen -S MTA_def /home/mtadef/mta-server64 -screen 0 800x600x16 -ac
      exit 1

[Code] ....

When I try to start the service by the command "systemctl start mtadef" now, I returns me the message:

"Must be connected to a terminal."

View 5 Replies View Related

Debian Multimedia :: Brasero Forces Reinstall Of Systemd

Jan 2, 2016

A computer upgraded from 7.3 to 8.2 suffered a number of stability issues which were traced to systemd having replaced sysvinit in this version. Worst of these was that instead of shutting down it just cut the power instantly, causing disk corruption. Basically, from what I can find out, this systemd component seems like it works OK on a completely fresh install but causes multiple issues if it finds its way onto an updated system. I found some instructions on reinstating sysvinit, which cured the issues.

However, on attempting to install the Brasero CD/DVD app via synaptic, I notice that this will force reinstallation of systemd as a dependency, even though it's been locked-out of updates. Luckily I spotted this in time and cancelled. You really wonder why a CD writing app would need to do this. I certainly seems rather naughty for any desktop package to be changing system startup code in a manner which could break the OS.

At the moment I'm not sure if it's the only app which does this -although k3b seemingly does not. Any thoughts on this gotcha, and how to prevent a repeat, other than being extremely careful when installing anything?

View 3 Replies View Related

Debian Installation :: Multiple SystemD Errors After Upgrade From Wheezy

Mar 3, 2016

Recently I upgraded my machine from wheezy to jessie.

Everything went smooth until the point that I restarted the node.

During startup I'm getting the following message which is flooding the screen:

Code: Select allsystemd-journald[296]: Failed to forward syslog message: Connection refused

After waiting a long time (the message above still continues to flood the screen), I'm being prompted with the following:

Code: Select allGive root password for maintenance (or type Control-D to continue):

If I press Ctrl+D the boot process continues and finally boots normally.

What I can do to avoid pressing Ctrl+D during the boot process?

I'm assuming that it must be a startup service which is failing but I'm unable to trace which exactly is that.

I'm attaching the full log [URL] ....

View 8 Replies View Related

Debian Multimedia :: Stuck At Grub Rescue When Remove Systemd

Jan 10, 2015

I thought I'd have a go at putting back sysvinit to run the start up daemons, after I discovered that upgrading to jessie removed it and slapped on systemd.

I didn't have any problems at all with systemd, infact it was pure speed at start-up, but after some reading I thought I'd like to go back to usual start-up scripts.

What I did was to boot a Live Debian and mount and chroot into my Debian system, then I ran

Code: Select allsudo apt-get remove --purge --auto-remove systemd
sudo apt-get install sysvinit-core sysvinit sysvinit-utils

On reboot, I hit a grub rescue prompt which says error: file not found.

Trying the methods to get that sorted out gets stuck with "unknown file system" after I use ls and ls(hd1,msdos2) -as well as other combinations - it only seems to work for a plugged in flash drive.

Then I chroot again and run update-grub and grub-install /dev/sdb but reboot still stops at grub rescue.

So I wonder, firstly, why replacing systemd mucked up grub. Then, besides re-install of systemd, how do I get a booting system?

View 5 Replies View Related

Debian :: Systemd Failing To Start System - Recovery Mode Fine

Nov 5, 2015

My previously running debian system recently started failing with systemd failure messages as some services are being started. It never completes. I can log into recovery mode.

I added systemd.log_target=kmsg systemd.log_level=debug into my grub parameters.

After I do that all that I see scrolling down the page on boot are:

systemd-journald[36] /dev/kmsg buffer overrun, some messages lost
and the occasional
systemd[1] Looping too fast Throttling execution a little

Is there a way that I can boot without systemd using sysvinit?

View 4 Replies View Related

Debian Installation :: Dist-upgrade From Wheezy (using Systemd) To Jessie Hangs

Nov 19, 2014

I have done on previous releases, but this time it hangs on me. It's "only" a Virtualbox, so I can reproduce it.

The wheezy already runs systemd, and is fully updated to to latest packages. Does not run any graphical.

Edits the source.list and does
$ apt-get update
$ apt-get upgrade # Did on one upgrade
$ apt-get dist-upgrade

It starts to upgrade (complains about missing version in libpgp-error), libc is installed, but at some point the systemd is running at high CPU and a dpkg seems to be stalled.

Should I disable systemd on wheezy before? This might not have been tested so much.

View 10 Replies View Related

Debian Installation :: Systemd - Automount Windows Partition / USB Devices In Jessie

May 11, 2015

There seems to be no documentation on how to automount partitions and USB devices under systemd in Jessie. (Overall, systemd entirely lacks any useful documentation or GUI configuration tools -- all very cryptic and hidden.)

I created custom files to enable automounting. I put them in /etc/systemd/system -- this may not be the right place, but it works.

Kernel note:
This does not work under the old Wheezy kernel linux-image-3.2.0-4.

To automount my Windows partition so I can access its files, I created:
/etc/systemd/system/media-windows.mount

The name of the file must match the mount point -- in this case, /media/windows

My file notes the device and file type, plus an fmask option so all the Windows files don't seem to be executable:

[Unit]
Description = windows mount to /media/windows
[Mount]
What=/dev/sda1
Where=/media/windows
Type=ntfs-3g
Options=fmask=111
[Install]
WantedBy=multi-user.target

The file ownership must be root.root. Apparently it doesn't need to be executable.

After creating, enable with:

sudo systemctl enable media-windows.mount

and it will mount on the next boot.

I read elsewhere that the before running the enable command you should run a start command:

sudo systemctl start media-windows.mount

but that didn't work for me.

View 2 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved