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.
My plex media server suddenly stopped working after years of no hassle use. This is the output of cat /proc/version = Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.65-1+deb7u2
My problem is similar to this forum thread viewtopic.php?f=5&t=121945 where I can get it to start by running Code: Select all/usr/sbin/start_pms & but it's not my normal server configuration. I added a couple files to it and it seems to work except it doesn't start when I reboot. I have to run that command again.This is the init script I've been running for years...
Code: Select all----
#!/bin/sh
### BEGIN INIT INFO
# Provides: plexmediaserver
# Required-Start: $remote_fs $syslog $networking
# Required-Stop:
[code]....
My Debian skills are lacking to know how to proceed with troubleshooting what could have happened. Everything else seems fine, I just can't seem to get this application to run at startup or get back my old configuration...
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?
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.
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"
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 View Relatedmy 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.
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.
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] ....
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] ....
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 ?
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 RelatedI'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
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.
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]....
I would appear that I recently installed linux-image-2.6.32-5-amd64. Since then I have noted that my HP media bar up top doesn't work. This means I can't enable/disable wireless. From an lspci output, it still sees the hardware, and it's loaded, however, not functioning. Should I be looking at rolling the kernel back, or work on getting it working via some other means? Any liveCD I've tried doesn't seem to be able to get it going either. So I'm under the assumption here it is the kernel version, and not a hardware problem.
lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) .....
Also tried this to no avail:
sudo apt-get install rfkill
rmmod iwlagn
rfkill block all
rrfkill unblock all
modprobe iwlagn
rfkill unblock all
ifconfig wlan0 up
SIOCSIFFLAGS: Unknown error 132
rfkill list
2: phy2: Wireless LAN
Soft blocked: no
Hard blocked: yes
jeff@optiplex:/media$ ls -l
total 124
lrwxrwxrwx 1 root root 6 Apr 7 14:46 cdrom -> cdrom0
drwxrwxr-x 2 root root 4096 Apr 7 14:46 cdrom0
[code]....
I have some general question with with quite an impact for the system I use I have a media server with 2 raid1 mirrors of 2 1 To disk aggregated with lvm and used by a big 2 To ext3 partition.A few days ago, munin (awesome!) started to send me notifications about smart attributes of some disks. Fyi, here's my hdparm.conf:
/dev/sda {
spindown_time = 54
}
/dev/sdb {
[code]...
regarding reliability and disk longevity, is it recommended to have them spin down while not used (most of the day, as these are storage unit for movies, pictures, documents..) or let them spin whatever.. ? Those are WD green and according to Tom' Hardware, the consumption is only slightly greater in idle compared to standby. The other question, (boat one as we say in french ) what is the best configuration here ? My 2 raid 1 stripes, or a raid 5 ? I know that two disks kill the raid 5, and they have to be of the same stripe to kill the lvm on the raid1, but what are the odds ?
I thought this might interest someone out there:[URL].. I used SD cards with MBR formatted as ext2 for backup. After I read these articles, I reformatted my cards with GUID Partition Table and ext4 format. Now I make my backup in half the time!
View 2 Replies View RelatedI have got a debian (v3.16.7-ckt25-2) for server (without X). There is a br0 bridge connected to eth0 network device. It works fine when I start it manually by
Code: Select all# ifup br0 but I cannot start automatically at startup.
there was a missing line in /etc/network/interfaces:Code: Select allauto br0
I have vnc4server installed and I can get it to work on a desktop by desktop basis, but I can't figure out how to get it to run on startup. There isn't a script for vnc in /etc/init.d/ How do I go about creating one? Is there a better way to solve this problem?
View 4 Replies View RelatedI tried recompiling a new kernel yesterday (2.6.34) on my debian sarge box, but I ran into multiple difficulties. These difficulties forced me to do a double dist-upgrade to lenny. The new kernel was (seemingly) compiled without any hiccups, and I ran dpkg -i on both the image and the header debs. They didn't install properly into grub, but I think I managed to fix that manually.Next thing I did was rebooting the server. It refused to come back up. Luckily my ISP has recovery tools, so I managed to switch back to the old kernel. It boots just fine with that kernel, but the problem is that there is no ssh daemon running! I can access it through ftp and do limited jobs through php, but nothing big, as I have no root access.Now, enough backstory. My question is: How can I install openssh-server onto the server remotely? I cannot access the server personally, as the server is in a completely different country.
View 14 Replies View RelatedI've been trying to setup Plymouth on Debian Squeeze, but have only been partially successful: Plymouth works with shutdown (i.e. I see Plymouth after I tell the computer to shut down), but not when I start up my computer (before it reaches GDM). In other words, Plymouth seems to work with my graphics, but for some reason does not show up at startup (not even briefly, as far as I can tell). I've searched the forums and followed this advice, as well as the instructions found here: [URL] but neither of those worked. I'm running Debian Testing (Squeeze) on a Thinkpad X41, which uses "Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller" for graphics.
View 4 Replies View RelatedI've been using Debian since the early days of Lenny being testing as OS on the same Computer. Its a Acer Aspire Notebook with switches for wireless and bluetooth. While booting Lenny my wireless and bluetooth stayed off as long as I didn't switch them on. But since squeeze they get activated ( you can see it by looking at the LED's ) the moment after the grub screen. I now do have to turn bluetooth and wireless off by hand everytime which is quite annoying since I mostly use eth0.
how to disable bluetooth and wireless per default in a way I can simply turn them back on by using the switch?
how can i setup ddclient at startup i already configured the client all i need is to let it start on bootup
View 3 Replies View Relatedwhen my computer starts up (from boot, reboot, hibernate or sleep) the speakers give out an annoying "boom".I an using Debian testing (wheezy kernel 2.6.32-5-amd64), with a Dell XPS L701. Alsa is version 1.0.23, and sound is working fine, other than this little annoyance.
View 6 Replies View RelatedThe "System Settings/Startup Programs" window is large enough but the "Program" column is too narrow and it cannot be resized. The window can be dragged to make it larger but not the individual columns. It looks like a Java listbox with "Enabled = false" set. This occurs in Debian8 64 bit and also in Mint 17 and Mint LMDE2. I am surprised nobody else has raised the issue. I have a basic setup with 22" screen and 1680 x 1050 resolution. It occurs with Nouveau and NVidia drivers. It is not a critical bug so I have coped with it for 2 years but it would be nice to see it fixed. Unfortunately I could not upload a screen shot as "board attachment quota has been reached".
View 2 Replies View RelatedMy wireless in fresh Squeeze install would not connect automatically. I have to click on the network manager and enter the root password to connect every time I start up. I have "Enable Networking" and "Enable Wireless" checked in the Network Manager.
System>Preferences>StartupApplications>NetworkManager --- checked
NetworkManager>NetworkConnections>Wireless>[mywifinetwork]Edit>AutomaticallyConnect --- checked
There are only 2 lines now in /etc/network/interfacesauto loiface lo inet loopbackWhat should I do to get the NM to look for and connect wireless automatically at start up
I have a script that needs to start executing on startup. Because I originally wrote it for MacOSX I never cared to learn how to daemonize it (thanks launchd!). Are there any relatively easy ways to run it on startup on debian to?
View 2 Replies View RelatedWe have setup squeeze workstations with gnome, citrix receiver and vmware-view client. Which startup programs and daemons, for example avahi-daemon can be normally disabled or what is disabled on your workstations?
View 1 Replies View Related