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
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:
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.
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?
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.
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.
How can I change the automatic fsck execution at boot time to be above 30 boots? I reboot the system sometimes 3 to 4 times a day. Intel 3 GHz, tower, i386 lenny vmlinuz-2.6.31-686
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:
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"
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.
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:
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
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.
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?
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?
Code: slackpkg upgrade-all At the end, it asked me if what to do with the new and old configuration files. I chose to use the old file and keep the new ones. But when I reboot the system, it fails to restart saying "cannot find which tty". Looks like the old configuration files doesn't go well with the new upgrade. How can I use the new configuration file without wiping out my old configurations? What are the steps to retrieve the system back online?
In a squeeze box, I installed awstats and it's working like a charm. Its cron job update the awstats database every 10 minutes (as it runs as root). But I would like to be able to update the statistics from the browser as well. So I setup everything as required and I gave "read" access to "others" to every apache log file. Now, a couple of questions came to my mind:
1. Am I compromising server's security giving "read" access to "others" to apache log files?
2. Instead of giving "read" access to "others", I could add www-data user to adm group (as apache log files are owned by root:adm and permissions are rw-r----). Is this more secure than giving "read" access to "others"? 3. If the option would be giving "read" access to "others" at the end, a log file would be owned by root:adm and its permissions be rw-r--r--. As apache rotates its log files, when Apache create a new log file, does it preserve the permissions (rw-r--r--) or create it with the default permissions (rw-r-----)?
My usb stick with Debian only loads from the usb hub it's crazy. I just tried putting the usb stick onto a usb3 port in my desktop and also on a usb2 port even the one where the usb hub is connected to and it wont' load!. Same initramfs prompt happens as when connected on the laptop usb ports.
the usb hub has usb2 speeds so is not that the stick is under usb1.1 emulation.
I noticed that when my server boots up, it's network interface on eth0 is always down and I always must run the 'ifup eth0' command in order to get it to work for some reason. I checked my configuration and it looks legit to me...
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
[Code]...
Anyone know why my system is booting with out bringing up my eth0 interface? It's very annoying.
First of all, my computer is running Debian Jessie. uname -a gives me this output: Code: Select allLinux felix-PC 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux
So today I updated my system with aptitude update and aptitude upgrade, and there was few paquages that were updated. Among them was one "linux-image" or "linux-headers". I believe that it is linked to this security update: [URL].... .
During the time aptitude upgrade was running, I was simply surfing on Iceweasel. However, it seems that my system suddenly restarted, without asking me the permission or without notifying me. It really looked like I pressed the restart key, but I actually didn't. My computer battery was full charged and plugged in. So, I do believe that it is my system that rebooted himself after the aptitude upgrade was completed (or even during the upgrade, I don't know).
So my computer restarts, and brings me to GRUB menu: I boot Debian and then I get the usual [ OK ] ***** lines telling that the system boots normally. But this time, I get some errors:
Code: Select all[FAILED] Failed to set up automount Arbitrary Executable file format file system Automount point ... [FAILED] Failed to start load kernel module ... [FAILED] Failed to mount /boot/efi [DEPEND] Dependency failed for Local File Systems
I arrive then in Emergency mode with this message: Code: Select all Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode. Give root password for maintenance (or type Control-D to continue):
I tried systemctl default but it doesn't boot my system normally. I also tried Control-D but it just reprints the same message. And finally I typed journalctl -xb, which gives me a long log file (855 lines) that I do not understand.
I would give this log file, but it seems that my internet connexion is broken (because of the kernel, I mean), even with an Ethernet cable. So I can't connect with ssh to the computer I use at the moment, and I can't either send it to myself by mail. I tried to mount an usb key, but it seems that any key won't be mounted because of a kernel problem.
An obvious solution to my problem may be to come back to an older kernel version. However, only the lasted kernel version (x86_64 Linux 3.16.0-4-amd64) is installed. dpkg --list | grep linux-image gives me indeed:
Code: Select alliF linux-image-3.16.0-4-amd64 3.16.7-ckt11-1+deb8u3 amd64 Linux 3.16 for 64-bit PCs ii linux-image-amd64 3.16+63 amd64 Linux for 64-bit PCs (meta-package)
I do not know how to come back to an older kernel, as far as I haven't any internet connection and as far as I seem to not be able to load an usb key.
So, my issues since upgrading to Jessie seem to compound. When I fix one issue, two more arise. Right now, I have a full system disk. How it got so full. So I started poking around. I ran
Code: Select all find / -type f -size +50M -exec ls -lh {} ; | awk '{ print $NF ": " $5 }'
Found a few files I could delete, and did, but I also found Code: Select all/var/log/syslog.1: 33G /var/log/messages: 33G /var/log/user.log: 33G
What I find strange is that they're all exactly 33G each. So that accounts for the missing 99GB I deleted them, however only recovered 27Gb. Whats weird is when I type df -h I get
What are the tmpfs's and how can I reclaim that space, and what is /dev/dm-0 and why is that taking up so much space?
I have 2 LVGs vgdisplay -v
Code: Select allroot@SETV-007-WOWZA:~# vgdisplay -v DEGRADED MODE. Incomplete RAID LVs will be processed. Finding all volume groups Finding volume group "WOWZASERVER"
[Code] ....
After deleting the log files, I was able to regain access to my GDM session. But I still cant find out what /dev/dm-0 is, and where all the 75 GB is being taken up.
I just noticed, however, even though I can access the drive A-OK via browser, terminal, and web services (Our wowza) when I enter gParted I get this error for sda, my primary OS drive!
Code: Select all Libparted Bug Found!
Error informing the kernel about modifications to partition /dev/sda2 -- Invalid argument. This means Linux won't know about any changes you made to /dev/sda2 until you reboot -- so you shouldn't mount it or use it in any way before rebooting
Now that I'm in gParted I see 3 partitions: [URL] ....
It reports now, that I have used ALL of my disk space.
Post Log delete, and fresh reboot, this is what Code: Select alldf -h outputs
wants some sort of logging capability on the system. to have a log of every change to every file, although that might be a bit unwieldy. perhaps a simpler compromise would be some way of monitoring a few specific folders, and tracking all changes to them, including the user that did so. Particularly important is that it should be possible to work with access through samba, as we want to track what users on the network are creating or changing files. Is there functionality like this already built into debian or samba? is there a useful additional app to gather this information? or am I going to need to be grep'ing log files to present something useable?
I installed Lenny on a computer and set up grub to boot windows by default with a timeout of 0 Is there a way to interrupt the boot process so I can boot linux? Or can I boot from a flash drive somehow? PS: nothing to do with topic, but I just found out that the top 24 supercomputers run linux , and more besides. That is way cool. check out [URL]..
went through the tutorial on FedoraSolved for securing ssh. I installed denyhosts with yum and then tried to run it with the command line command"sudo /etc/init.d/denyhosts start" but I got the message"Job Failed. See system logs and 'systemctl status' for details [FAILED]"and in the application "services" in the applications menu,t shows an exclamation warning and says that "This unit has failed"
I have some errors when run the mount -all command: mount: wrong fs type, bad option, bad superblock on /dev/sdc5, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Failed to open /proc/filesystems: No such file or directory
I tried to compile a 2.6.33 kernel following Alien's guide.
I pretty much used the default values for every (NEW) option avaiable. I used "make localmodconfig" on my current config (zcat /proc/config.gz) and then tried to use "make menuconfig" to check if I could change anything. I didn't understand most of the options, so I skipped it. Then I used "make bzImage modules" and "make modules_install", copied the files mentioned on the wiki and run lilo.
But when I try to boot using my custom kernel, it gives an error like "Cannot remount read-only filesystem as read-write! This can cause serious problems."
If I try to continue the boot, it hangs when trying to launch the syslog script...
The new kernel entry on lilo.conf is:
Code: image = /boot/vmlinuz-custom-2.6.33 root = /dev/sda4 label = newkernel read-only just like the default kernel entry.
By the way, one thing I changed is the kernel compression format, which I set LZMA. But it didn't seem to be the problem, since it at least started...
Debian 8.2 .... Desktop is lxde BTW. It auto-mounts the drive, and sometimes it's writeable for a while, but then it all goes read-only out of the blue. su doesn't work. I tried installing autofs and it doesn't mount at all.
/var/log/messages:
Nov 20 11:05:37 debian kernel: [589471.166033] scsi31 : usb-storage 1-3:1.0 Nov 20 11:05:37 debian mtp-probe: checking bus 1, device 41: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3" Nov 20 11:05:37 debian mtp-probe: bus: 1, device: 41 was not an MTP device Nov 20 11:05:40 debian kernel: [589474.217399] scsi 31:0:0:0: Direct-Access PNY USB 2.0 FD 8192 PQ: 0 ANSI: 0 CCS
[Code] ....
syslog looks much the same.
I'm not an lxde fan. The file manager always was crashy. But I'm on an Acer Aspire, and too many desktop managers just can't deal with the screen ratio.
I'am using Ubuntu 10.10, and wish to install a Debian OS.I downloaded the file "debian-6.0.1a-amd64-netinst.iso.(My motherboard is a 945CG-F7 with INTEL PENTIUM DUAL CPU E2160)I recorded the file on CD as "iso" (following instructions from Internet).Grub tried to read the CD but than started Ubuntu OS.
