debian.org - broken Download link.
Hi! At the main page https://www.debian.org/, the Download link with Debian logo at the right part of the page is broken. https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.1.0-amd64-netinst.iso Leads to "Not Found". The requested URL was not found on this server. Apache/2.4.55 (Unix) Server at cdimage.debian.org Port 443
Re: debian.org - broken Download link.
Hi, Brad. The issue with a broken download link was in browser cache. It preserved link to previous 12.1 version in html. After force update by F5 the issue was resolved. P.S. It is so uncommon when robust technologies with low resource consumption are used, with SinglePageApplications no need to press F5, full data set downloaded per each request.
install Kernel and GRUB in chroot.
Greetings! After: 1. Creating GPT table and GPT partition with fdisk. 2. Copy data with a debootstrap. 3. Chroot into newly creating system. I need to prepare that system for booting. 1. Install Kernel. 2. Install GRUB and Configure. 3. Add changes to UEFI to start booting. And at the point two (Install GRUB) I a little bit confused. 1. Need to create ESP, and put GRUB there. 2. Need to configure GRUB to select appropriate kernel and ramdisk. Could you help me a little bit? How to create a ESP partition and mount it to /boot? If a ESP partition a simple Partition formatted to FAT32? How GRUB would understand where to be install and where is the kernel? And the last one. If I want to step back. And just use a USB stick with predefined image, what kind of partition table I should create there MBR or GPT? Thank you!
Re: install Kernel and GRUB in chroot.
> Why don't you use the normal setup? Spend a lot of time on research, it would be nice to finish. I made experiments with a FlashDrive, and create GPT there, if I want to use standard Debian Image how I should partition that flash drive (MBR, GPT)? > Do you need a special configuration here or is the default just fine? Need just working one. But I am confusing about how GRUB would get a plenty of things related to filesystem, kernel location and so on. > If you create a separate boot partition (do you really need it?), it must be mounted at /boot. Here where the mess starts. How GRUB and Kernel would get information about all this mounting points during the Boot.
Re: install Kernel and GRUB in chroot.
Huge thanks. Your message starts the understanding. And as well give a plenty of texts to read. > EFI/debian/grub.cfg on the EFI System Partition contains filesystem UUID where grub files reside. All parts are simple But when compounding them together become messy. In the Manjaro: /boot/EFI/Majaro/grub64x.efi - binary to start by UEFI. /boot/grub/grub.cfg - shell (?) script with configurations. /boot/vimlinuz.* - the kernel. And if call a `lsblk`. Only a /boot/efi with a binary is a separate partiton. Things become more clear.
Re: install Kernel and GRUB in chroot.
Hi Tim. The community is so kind. So. > I'm not exactly sure what you're doing. Understand how GRUB works, to boot myself. 1. Trying to install Debian on the Flash. 2. Use it by the Debootstrap. 3. Now I want to boot using that Flash. Looks like a caught the thread. 1. ESP is a partition that stores GRUB Binary. /boot/EFI/Name/grub64.eif 2. ==>BAM<== some how that binary knows the system partition. 3. At the system partition there is a /boot/grub/grub.cfg 4. And at that /boot/grub/grub.cfg is UUID and etc. to start Booting. But the question is on the step 2. /boot/EFI/Name/grub64.efi knows where to start /boot/grub/grub.cfg that resides at the absolutely different partition. Interesting. But the question already asked. Now it possible to find the answer. Thank you!
Re: install Kernel and GRUB in chroot.
> Do you want to install the OS on it? Eventually no, I do not want OS on the Flash Stick. The Flash Stick is only a testing place. I want OS at the SSD. Now I am wondering how to prepare the Flash Stick to write LiveImage on it. Because I already created a GPT table on that Flash and use debootstrap. Looks like need to create a new parition and copy LiveImage there. Need additional research what to do with a FlashStick with several partitions to make a LiveCD from it. > Do you want an encrypted system? No. I do not need this abstraction layer now.
Re: install Kernel and GRUB in chroot.
Going to read carefully. https://www.debian.org/releases/buster/amd64/ch04s03.en.html Interesting that Buster has more documentation than current release.
Re: install Kernel and GRUB in chroot.
> Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the ESP partition on the USB stick. As I understand right now `dd` command applied to a device will copy all information including partitions table. Thus: dd if=debian-xx.iso of=/dev/sdb bs=4M status=progress; sync Would just create a copy of device, with FileSystem and PartitionsTable.
Re: install Kernel and GRUB in chroot.
> Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the ESP partition on the USB stick. Yep. `dd` copy partitions table. Amazing. ``` dd will simply recreate the old partition scheme, as it is a bitwise copy & applies no 'intelligence' to the operation. ``` https://askubuntu.com/a/847533
Re: install Kernel and GRUB in chroot.
Main question is resolved. GRUB knows how to reach grub.cfg because grubx64.efi binary has the UUID and path to grub configurations. 1. sudo blkid; 2. sudo bash 3. cd /boot/efi/EFI/Mangaro 4. strings grubx64.efi 5. And at the output of strings there is UUID and /boot/grub. Summary: GRUB installation not only involves configuration of text files, but also it involves generating data in binary grubx64.efi.
Re: install Kernel and GRUB in chroot.
sudo -i Thank you! I am unsure what UUID you mean. At Manjaro: grubx64.efi is at the sdb1 - EFI vfat /dev/sdb1 grub.cfg is at the sdb2 - crypto_LUKS /dev/sdb2 grubx64.efi contains data UUID=""a8...b7" of /dev/sdb2 which is TYPE="crypto_LUKS". `blkid` output: /dev/sdb2: UUID="a8...b7" TYPE="crypto_LUKS" PARTUUID="8...5" `strings /boot/efi/EFI/Manjaro/grub64x.efi` output: cryptomount -u a8...b7 (cryptouuid/a8...b7)/boot/grub I have a Manjaro installed, and what to migrate to Debian. That involves exploration of Booting order. In the Manjaro GRUB installation mounting point for ESP (sdb1) is: /boot/efi And the grub.cfg is /boot/grub/grub.cfg The grub.cfg located at the crypto partition sdb2. Manjaro has different GRUB installation scheme from Debian.
Re: install Kernel and GRUB in chroot.
> It would not work with secure boot Yes. But secure boot is usually turned off. It is a standard advice during Linux installation.
Difficulties with PS1.
Greetings! Why variable PS1 dose not change when set it before a command: Like this: A="a1" LANG="C.UTF-8" PS1="new" B="b2" bash --noprofile $A, $B, $LANG -changed, $PS1 - not. Works only when I explicitly set in current process. export PS1="(chroot) $PS1" Is not this syntax: VAR="..." VAR1="..." command Set an environment variables? Thank you!
Re: Difficulties with PS1.
PS1="Works $PS1" bash --noprofile --norc https://stackoverflow.com/questions/9357464/how-to-start-a-shell-without-any-user-configuration
Aptitude back to neutral state of a package.
Hi. When I take a look at a package line in the SecurityUpdates of the TextUserInterface of Autitude I see `PackageName i A` if press `u` => iuA => Update if pres `-` => idA => Delete if press `_` => ipA => Purge if press `=` => ihA => Hold But how to go back to `i A`? I am using Ctrl+u to just undo. But deeply unsatisfied by this approach. Skim over the documentation for a while but cannot find key to go back to empty state. Thank you.
Yes. Keep is the answer. ":" => "i A"
Yes. Thank you! if press `:` => i A => Keep (What I was seeking for) if press `+` => iuA => Update if pres `-` => idA => Delete if press `_` => ipA => Purge if press `=` => ihA => Hold
How to force Hewlett Packard ScanJet 2410c work?
Hi! Description:Debian GNU/Linux 12 (bookworm) Scanner: Hewlett Packard ScanJet 2410c $ scanimage --list-devices OUT: device `genesys:libusb:003:012' is a Hewlett Packard ScanJet 2400c flatbed scanner See as 2400c now 2410c. $ scanimage --device-name=genesys:libusb:003:012 --format=png --output-file=1.png OUT: scanimage: open of device genesys:libusb:003:012 failed: Invalid argument $ scanimage -T Output format is not set, using pnm as a default. scanimage: open of device genesys:libusb:003:012 failed: Invalid argument Enter as a root. $ sudo -i # scanimage -T Output format is not set, using pnm as a default. scanimage: open of device genesys:libusb:003:012 failed: Invalid argument The same. Cannot make this device work. It worked at the Manjaro out of the box, now I am a Debian User and need to make it run here. Thank you!
Large files support and libc
Hello! I'm primarily FreeBSD user so excuse me if my question is too stupid for debian folks. I've used Debian 2.2 for telephony tasks last year with kernel-2.2.18 but last week I've tried to upgrade it to woody and kernel-2.4.18 because of large files support. System was upgraded smoothly but I can't make LFS work. According to many HOWTOs that I found on the web I have built and have installed kernel image and headers with make-kpkg. Next I built glibc with new kernel headers: pharaoh# uname -a Linux pharaoh.amur.dti 2.4.18 #3 Mon Dec 2 11:10:00 YAKT 2002 i686 unknown unknown GNU/Linux pharaoh# export LINUX_SOURCE=/usr/src/kernel-headers-2.4.18; apt-get --build source glibc [skip] pharaoh# dpkg -i libc6_2.3.1-5_i386.deb libc6-dev_2.3.1-5_i386.deb locales_2.3.1-5_all.deb Next I rebuilt coreutils for testing: pharaoh# apt-get --build source coreutils [skip] pharaoh# dpkg -i coreutils_4.5.3-4_i386.deb [skip] pharaoh# dd if=/dev/zero of=testfile bs=1024 count=450 File size limit exceeded Anyway 2G size limit still exists. What's wrong? Am I missing something? Any suggestions? -- /Dmitry Krasnov P.S. Please reply to me directly or CC. I'm off the list. P.P.S. Sorry for my awful english. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Large files support and libc
On Friday 13 December 2002 15:45, you wrote: > On Fri, 2002-12-13 at 01:08, Dmitry Krasnov wrote: > > pharaoh# dd if=/dev/zero of=testfile bs=1024 count=450 > > File size limit exceeded > > Yup finishes sucessfully here. All I did was build a 2.4 kernel. Im > using the standard glibc that comes with Debian/SID but I have a server > running Woody, and that works as well. What file system are you > running? Both of mine are on ext3. If you are runnning ext2 that may be > the problem(though I think even ext2 has LFS now, I might be wrong > though). I use three partitions with old ext2 and two partitions on two 60G disks, both with ext3. Same results with any. -- /Dmitry Krasnov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Large files support and libc
On Saturday 14 December 2002 00:32, you wrote: > Thus spake Dmitry Krasnov: > > pharaoh# dd if=/dev/zero of=testfile bs=1024 count=450 > > File size limit exceeded > > > > Anyway 2G size limit still exists. What's wrong? Am I missing something? > > Any suggestions? > > My first reaction is to wonder of PAM limits are getting in the way... > Have you made any changes to /etc/security/limits.conf with regards to > fsize? Also, what does ulimit -f say? There is no active lines in my /etc/security/limits.conf. Everything is commented. ulimit -f says "2097151". Done it! If I change ulimit -f to "unlimited" any tests works ok. Thank you very much! But I can not find any config files where "2097151" limit is set. It is active for any user even for root. What I must do to set up "unlimited" limit :) for everyone by default in right way? Rebuild PAM? Or something else? -- /Dmitry Krasnov P.S. Sorry for my awful english. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Writing Drivers? Info Appreciated!
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Timothy Hospedales > Sent: Thursday, June 03, 1999 10:19 AM > To: debian-user@lists.debian.org > Subject: Writing Drivers? Info Appreciated! > > > Anyway, if this sort of thing is possible could someone > point me to a > winblows program to use to examine what gets sent over a port? Try Soft-Ice from NuMega software. It's kinda standard hacker/cracker tool. Not freeware, unfortunately. --BEGIN GEEK CODE BLOCK- Version: 3.1 GS d+>d-- s++:>++:+ a- [EMAIL PROTECTED] UL$ P++> L++>L !E W+@ N(-) o? K? w$>--- O-(+) M>+ V-- PS+ PE Y+>++ PGP+>++ ?t 5 X-- R tv- b+++> DI+++ D++ G++ e+> h---(+) r++ y+++ --END GEEK CODE BLOCK- > > Thanks! > Tim >
unsibscribe
Hello , Best regards, Dmitry mailto:[EMAIL PROTECTED]
RE: Gnome missing dependencies
> -Original Message- > From: Craig R. Hodges [mailto:[EMAIL PROTECTED] > Sent: Monday, May 10, 1999 12:24 AM > To: debian-user@lists.debian.org > Subject: Gnome missing dependencies > > > When trying to install (unstable) Gnome using the directions at > http://www.gnome.org/start/getting_debian.shtml > Apt-get reports: > > Sorry, but the following packages are broken - this means they have unmet > dependencies: > gnome-panel: Depends:libghttp1 Depends:libgtop1 > gnome-utils: Depends:libglib1.1.13 Depends:libgnome31 > Depends:libgtk1.1.13 Depends:libgtop0 > > I can't seem to find libghttp1, libglib1.1.13, libgtk1.1.13! > > Does anyone know where to find them or a different way to install > gnome-panel and gnome-utils? I had exactly the same problem. Being too lazy to compile it myself, I just grabbed the Rad Hat packages from one of Gnome mirrors and converted them with 'alien' and then installed with dpkg (yes, I know that "alien -i" would also install them for me). It mostly worked, though some of the Gnome features do not seem to work, like adding applets to the panel (or maybe I screwed the configuration in the process) Hope this helps. bst rgds, Dmitry --Optimists study English. Pessimists study Chinese. Realists study Kalashnikov. - russian conventional wisdom
tetex install problem: fmtutil failed
Hi, I have upgrade my system from slink to potato, but during installation of `tetex-base' package I get the following message Preparing to replace tetex-base 1.0-4 (using tetex-base_1.0-4.deb) ... Unpacking replacement tetex-base ... Setting up tetex-base (1.0-4) ... texhash: Updating /usr/local/lib/texmf/ls-R... texhash: Updating /var/lib/texmf/ls-R... texhash: Updating /var/spool/texmf/ls-R... texhash: Done. Running initex. This may take some time. ... fmtutil: `tex -ini -fmt=latex -progname=latex latex.ini' failed. Output of initex is in /tmp/texE3D03P Although `tetex-base' package marked as installed, but `babel' package does not work. When I try compile by latex any text that used `babel' package I get the following error: ! Undefined control sequence. l.20 \ProvidesLanguage {russianb} ? Any advice would be appreciated, Dmitry texE3D03P.gz Description: Binary data
Re: VI and Ispell
Jack Morgan <[EMAIL PROTECTED]> wrote: JM> How cn i use Ispell in VI? I'm using VI as my editor for Mutt and want to be JM> able to JM> check my spelling. I'm a VI newbie so any help is greatly appreciated ;-) Try to use this script author: Andrew Rodionoff <[EMAIL PROTECTED]> (need tcl support in vim) .vimrc --- tclfile ~/.vimrc.ispell.tcl command! -nargs=1 IspellDict tcl Ispell_Dict fun! IspellLine() tcl Ispell_Line [::vim::expr line(".")] return "" endfun hi IspellCombo gui=underline guifg=yellow guibg=none cterm=underline ctermfg=yellow ctermbg=none term=underline hi IspellError gui=underline guifg=red guibg=none cterm=underline ctermfg=red ctermbg=none term=underline fun! Ispell_on() inoremap =IspellLine() endfun fun! Ispell_off() if mapcheck("", "i") == " =IspellLine()" iunmap endif endfun augroup ispell " au! " au filetype mail call Ispell_on() " au filetype tex call Ispell_on() " au WinEnter,BufEnter * call Ispell_off() au WinEnter,BufEnter *.tex call Ispell_on() au WinEnter,BufEnter *.txt call Ispell_on() augroup END .vimrc.ispell.tcl # This is on-the-fly spellchecking support module for Vim # Author: Andrew Rodionoff <[EMAIL PROTECTED]> Copyleft (x) 2000 # Disclaimer: ->Insert your favourite disclaimer here<- # # TODO: # Error-handling set Ispell(dictionary) russian set Ispell(binary) /usr/bin/ispell proc Ispell_Dict {dictname} { global Ispell if {[info exists Ispell(pipe)]} { close $Ispell(pipe) set Ispell(dictionary) $dictname Ispell_start_server } else { set Ispell(dictionary) $dictname } } proc Ispell_start_server {} { global Ispell puts "Starting Ispell process..." if {[info exists Ispell(dictionary)]} { set dict_string "-d $Ispell(dictionary)" } else { set dict_string "" } set Ispell(pipe) [open "|$Ispell(binary) -a $dict_string" r+] set Ispell(version) [gets $Ispell(pipe)] if {$Ispell(version) == ""} { puts vimerr "Could not start ispell server. Check your dictionary name." } fconfigure $Ispell(pipe) -blocking off -buffering line fileevent $Ispell(pipe) readable Ispell_process_filter } proc Ispell_process_filter {} { global Ispell set Ispell(responce) [read $Ispell(pipe)] if {[string length $Ispell(responce)] <= 1} { return } switch -- [string index $Ispell(responce) 0] { \- { $::vim::current(buffer) command "syntax match IspellCombo \"\\<$Ispell(word)\\>\"" } \& - \# { $::vim::current(buffer) command "syntax match IspellError \"\\<$Ispell(word)\\>\"" } \+ - default { } } } proc Ispell_Word {word} { global Ispell if {![info exist Ispell(pipe)]} { Ispell_start_server } if {$word == ""} { return } set Ispell(word) $word puts $Ispell(pipe) $word vwait Ispell(responce) } proc Ispell_Line {line} { set words [split [$::vim::current(buffer) get $line] "<>~`'., [EMAIL PROTECTED]&*()_|-=+\\\/\""] foreach w $words { Ispell_Word $w } } - JM> TIA JM> -- JM> Jack Morgan Debain GNU/Linux JM> Email:[EMAIL PROTECTED] JM> Web-site: www.mandinka.org -- Sed-off e-mail: [EMAIL PROTECTED]
uploading & apache
Hi! I run apache to upload files on my computer (with web-form), but after upgrading to apache-1.3.9-13.1 this form doesn't work. If there are the tag then apache's child process gets a segfault after pressing button SUBMIT. Does anybody have the similar problem? or not?
Re: DRI in XFree 4 with i810
On Thu, Nov 23, 2000 at 11:33:55AM +0530, Viral wrote: > I've got XFree 4 starting up with DRI (I'm running 2.4-test11, with > the > agpgart and dri modules). > > I can run the gears demo, but quake 3a fails to run. > I get some Gart errors in my log. > I'm attaching my log file. Does anyone know whats the problem. > DRIUnlock called when not locked > (WW) AGPIOC_ACQUIRE failed (Device or resource busy) > (EE) GARTInit: AGPIOC_INFO failed (Invalid argument) I have exactly same errors, and it makes my X crash. But it is not related to Quake3 and I can't reproduce it. Dmitry Borodaenko
Re: stable - testing
KO> "stable" with "testing". I did that, and ran dselect to browse through KO> the changes and found a couple of problems KO> 1: Its plan to upgrade my stable system generates some dependency KO> issues. It tells me that; KO> lwrsed recommends libnss-lwres libnss-lwres does not appear to be KO> available KO> gnome-panel recommends gnome-applets (>=1.4.0-1) gnome-applets does KO> not appear to be available Add lines for "unstable" to your sources.lst as well. That is, you should have lines for "testing" first, then lines for "unstable", and then - for "stable". Packages that are not available in "testing" (f.e. gnome-applets) are in "unstable", and that should solve the problem -- Dmitry Astapov //ADEpt (mail-to: [EMAIL PROTECTED])
Re: Memory figures
NR> memory should be at most 46 MB, and not 98 MB as 'free' NR> says. In fact, figures you provided show that only 20M are used. Find some reading about how VM subsystem works, or just take a loot on second line of 'free' output, the one with "+/- buffers" in it. Amount of "used" memory in the first line includes size of filesystem cache and "dirty" buffers, so it is perfectly OK to have all your spare RAM used as disk cache. -- Dmitry Astapov //ADEpt (mail-to: [EMAIL PROTECTED])
woody+cisco pci342
Hello, Did somebody have any problems with cisco PCI342 aironet card plugged to supermicro x5dpa-gg MB? Woody(2.4.20) with own airo.o works, but shows terrifying quantity of frame errors (/proc/drivers/aironet/statistics shows acceptable quantity) and stop working when turn to promiscouos mode by tcpdump. With drivers from Cisco.com unit stops working any time from boot airo.o and writes "airo: can't find FID. " What is it FID? Is there somebody who use cisco PCI342 and woody? Thanks in advance. -- wbr, Dmitry Lukin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Some services cannot start at boot time because /run is not initialized
Dear Debian community, I have noticed that all failed services were missing some directories under /run directory. I checked the service which is supposed to create them: * systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) systemd[1]: sysinit.target: Found ordering cycle on systemd-tmpfiles-setup.service/start systemd[1]: sysinit.target: Found dependency on local-fs.target/start systemd[1]: sysinit.target: Found dependency on zram-setup@zram1.service/start systemd[1]: sysinit.target: Found dependency on sysinit.target/start systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start and it looks like there is problem in zram-setup@zram1.service which I configured like that: [Unit] Requires=dev-%i.device After=dev-%i.device Before=local-fs.target [Install] WantedBy=local-fs.target # systemctl show -p Requires,Wants,Requisite,BindsTo,PartOf,Before,After local-fs.target Requires=home.mount -.mount var.mount Requisite= Wants=systemd-fsck-root.service zram-setup@zram0.service zram-setup@zram1.service systemd-remount-fs.service BindsTo= PartOf= Before=binfmt-support.service sysinit.target systemd-machine-id-commit.service systemd-tmpfiles-setup.service networking.service systemd-tmpfiles-clean.service console-setup.service After=run-user-1000.mount zram-setup@zram0.service root.mount -.mount tmp.mount zram-setup@zram1.service systemd-fsck-root.service systemd-remount-fs.service home.mount var.mount local-fs-pre.target Even though I don't see any conflict with dependencies, it is confusing systemd. Any idea concerning how to fix that is welcomed. On 2020-06-29 01:37, Dmitry Katsubo wrote: > Dear Debian community, > > I hit the similar problem but this time with /run folder. Few services have > failed to start: > > # systemctl status php7.0-fpm.service > Jun 24 23:09:48 debian php-fpm7.0[893]: [24-Jun-2020 23:09:48] ERROR: unable > to bind listening socket for address '/run/php/php7.0-fpm.sock': No such file > or directory (2) > Jun 24 23:09:48 debian php-fpm7.0[893]: [24-Jun-2020 23:09:48] ERROR: FPM > initialization failed > Jun 24 23:09:48 debian systemd[1]: php7.0-fpm.service: Main process exited, > code=exited, status=78/CONFIG > Jun 24 23:09:48 debian systemd[1]: php7.0-fpm.service: Failed with result > 'exit-code'. > Jun 24 23:09:48 debian systemd[1]: Failed to start The PHP 7.0 FastCGI > Process Manager. > > # systemctl status motioneye.service > Jun 24 23:09:47 debian systemd[1]: Started motionEye Server. > Jun 24 23:09:48 debian meyectl[895]: INFO: hello! this is motionEye > server 0.41 > Jun 24 23:09:48 debian meyectl[895]: CRITICAL: pid directory "/run/motioneye" > does not exist or is not writable > Jun 24 23:09:48 debian systemd[1]: motioneye.service: Main process exited, > code=exited, status=255/EXCEPTION > Jun 24 23:09:48 debian systemd[1]: motioneye.service: Failed with result > 'exit-code'. > > # cat /etc/tmpfiles.d/php.conf > d /run/php/sessions 1733 root root > > # cat /etc/tmpfiles.d/motioneye.conf > d /run/motioneye 0750 motion motion > > Just after the boot I have inspected /run folder. It was created/mounted > correctly and there have been a lot of files/directories there. I suspect that > all services that have created the necessary directory under /run were able to > start normally. Few of them which relied on existence of specific directory, > have failed to started. After I have replayed the corresponding instructions > for > tmpfiles.d, the services have started normally. > > I have a feeling that systemd-tmpfiles was executed before /run was mounted. > > Needless to note that the problem is not persistent: sometimes OS boots > without > a single failed service. > > How can I debug the problem? > > Thank you! > > On 2020-05-18 02:39, Dmitry Katsubo wrote: >> On 2020-05-11 20:11, Darac Marjal wrote: >>> On 11/05/2020 08:40, Reco wrote: >>>>Hi. >>>> >>>> On Mon, May 11, 2020 at 09:33:59AM +0200, Dmitry Katsubo wrote: >>>> >>>>> root@debian:~ # systemctl status binfmt-support >>>>> * binfmt-support.service - Enable support for additional executable >>>>> binary formats >>>>>Loaded: loaded (/lib/systemd/system/binfmt-support.service; enabled; >>>>> vendor preset: enabled) >>>>>Active: failed (Result: exit-code) since Sun 2020-05-10 21:54:27 CEST; >>>>> 10h ago >&g
Re: networking.service fails
: wlan0: AP-ENABLED Apr 4 00:37:29 debian hostapd[1627]: wlan0: interface state UNINITIALIZED->ENABLED Apr 4 00:37:29 debian kernel: [ 22.487228] br0: port 3(wlan0) entered blocking state Apr 4 00:37:29 debian kernel: [ 22.487233] br0: port 3(wlan0) entered disabled state Apr 4 00:37:29 debian kernel: [ 22.487279] device wlan0 entered promiscuous mode Apr 4 00:37:29 debian kernel: [ 22.487298] br0: port 3(wlan0) entered blocking state Apr 4 00:37:29 debian kernel: [ 22.487299] br0: port 3(wlan0) entered forwarding state Apr 4 00:37:29 debian kernel: [ 22.676802] br0: port 1(eth0) entered disabled state Apr 4 00:37:29 debian kernel: [ 22.676917] br0: port 2(eth1) entered disabled state Apr 4 00:37:29 debian systemd[1]: Failed to start Raise network interfaces. Apr 4 00:37:29 debian systemd[1]: networking.service: Failed with result 'exit-code'. Apr 4 00:37:29 debian systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Apr 4 00:37:31 debian kernel: [ 24.515701] r8169 :02:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx Apr 4 00:37:31 debian kernel: [ 24.515722] br0: port 1(eth0) entered blocking state Apr 4 00:37:31 debian kernel: [ 24.515727] br0: port 1(eth0) entered forwarding state What confuses me is that hostapd is configured to run after network.target, but in fact is running together with it. Maybe there is a side effect when hostapd adds wlan0 to br0? On 2021-02-17 15:38, Gary Dale wrote: > On 2021-02-17 08:28, Andrei POPESCU wrote: >> On Mi, 17 feb 21, 00:01:01, Gary Dale wrote: >>> On 2021-02-16 19:44, Dmitry Katsubo wrote: >>>> Dear Debian community, >>>> >>>> I am puzzled with the following problem. When my Debian 10.8 starts, the >>>> unit "networking.service" is >>>> marked as failed with the following reason: >>>> >>>> root@debian:~ # systemctl status networking.service >>>> *— networking.service - Raise network interfaces >>>> Loaded: loaded (/lib/systemd/system/networking.service; enabled; >>>> vendor preset: enabled) >>>> Active: failed (Result: exit-code) since Tue 2021-02-16 08:56:16 CET; >>>> 5h 27min ago >>>> Docs: man:interfaces(5) >>>> Process: 691 ExecStart=/sbin/ifup -a --read-environment (code=exited, >>>> status=1/FAILURE) >>>> Main PID: 691 (code=exited, status=1/FAILURE) >>> Debian/Busteris still using Network Manager not systemd to control the >>> network so I think the network.service shouldn't be used. >> Well, systemd as init is starting everything so that necessarily >> includes starting "the network", which in practice means starting >> whatever network management framework is in use[1]. >> >> The 'networking.service' service is part of ifupdown, Debian's default >> network management framework (Priority: important). >> >> Network Manager is Priority: optional and typically installed as a >> Depends/Recommends of Desktop Environments. >> >> [1] this is applicable even for systemd's own network management >> framework systemd-networkd, which is included in the 'systemd' Debian >> package, but not activated by default. >> >> Kind regards, >> Andrei > Sorry, it was midnight when I replied. However the failure is likely still > due to the interfaces misconfiguration - probably reporting a failure to > raise a non-existent interface. > On 2021-02-17 07:55, Reco wrote: > Try running this: > > ifdown -a --force > ifup -a -v > > Last command should show you the source of the trouble. > > Reco Reco, here is the log: # ifdown -a --force; ifup -a -v /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/bridge run-parts: executing /etc/network/if-pre-up.d/ethtool run-parts: executing /etc/network/if-pre-up.d/hostapd run-parts: executing /etc/network/if-pre-up.d/wireless-tools run-parts: executing /etc/network/if-pre-up.d/wpasupplicant ifup: configuring interface lo=lo (inet) /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/bridge run-parts: executing /etc/network/if-pre-up.d/ethtool run-parts: executing /etc/network/if-pre-up.d/hostapd run-parts: executing /etc/network/if-pre-up.d/wireless-tools run-parts: executing /etc/network/if-pre-up.d/wpasupplicant /sbin/ip link set dev lo up /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-autoipd run-parts: executing /etc/network/if-up.d/ethtool run-parts: executing /etc/network/if-up.d/wpasupplicant ifup: unknown in
Re: networking.service fails
16.861081] br0: port 2(eth1) entered disabled state 2022-04-10 12:37:16.289779 debian kernel: [ 18.637162] r8169 :02:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx What confuses me is that ifup is triggered before the interface is started – is that expected? Should systemd retry after interfaces are up? At the end of the day, br0 is created and functions just fine, so the system works, but networking.service is marked as failed. Thanks for any further ideas. -- With best regards, Dmitry
Re: networking.service fails
On 2022-04-11 07:56, Reco wrote: > Good news - it explains "ifup: unknown interface eth0" messages. > Bad news - this /e/n/i is not valid. > > The reason being - both eth0 and eth1 lack interface definitions, i.e. > have no "iface" stanzas. > > If you absolutely need both eth0 and eth1 in the UP state by the time > you create and bring up br0 you should either: > > 1) Define both eth0 and eth1 in /e/n/i like this: > > auto eth0 > iface eth0 inet manual > > auto eth1 > iface eth1 inet manual > > auto br0 > iface br0 inet static > address 10.0.1.100 > gateway 10.0.1.1 > netmask 255.0.0.0 > bridge_ports eth0 eth1 > bridge_maxwait 60 > > 2) Use pre-up and post-down hooks for br0, and remove both "auto eth0" > and "auto eth1": > > auto br0 > iface br0 inet static > address 10.0.1.100 > gateway 10.0.1.1 > netmask 255.0.0.0 > bridge_ports eth0 eth1 > bridge_maxwait 60 > pre-up /sbin/ip link set eth0 up > pre-up /sbin/ip link set eth1 up > post-down /sbin/ip link set eth0 down > post-down /sbin/ip link set eth1 down > > Reco Hooray, it worked! Thanks for pointing out the configuration error. After fixing it everything worked like a charm. Would be very tricky for me to locate the issue... If the configuration is invalid, networking.service could probably complain about that? I would be able then to resolve the issue myself. Just for my record the reference to documentation: https://wiki.debian.org/BridgeNetworkConnections#Configuring_bridging_in_.2Fetc.2Fnetwork.2Finterfaces -- With best regards, Dmitry
networking.service fails
Dear Debian community, I am puzzled with the following problem. When my Debian 10.8 starts, the unit "networking.service" is marked as failed with the following reason: root@debian:~ # systemctl status networking.service *— networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2021-02-16 08:56:16 CET; 5h 27min ago Docs: man:interfaces(5) Process: 691 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 691 (code=exited, status=1/FAILURE) however network is working just fine. I looked into /usr/lib/systemd/system/networking.service where TimeoutStartSec=5min and also set a big timeout for br0 in /etc/network/interfaces: auto lo auto eth0 auto eth1 iface lo inet loopback auto br0 iface br0 inet static ... bridge_ports eth0 eth1 bridge_maxwait 60 but still the error occurs each time. Relative dmesg logs are: Feb 16 08:56:16 debian systemd[1]: Starting Raise network interfaces... Feb 16 08:56:16 debian ifup[691]: ifup: unknown interface eth0 Feb 16 08:56:16 debian ifup[691]: ifup: unknown interface eth1 Feb 16 08:56:16 debian ifup[691]: Waiting for br0 to get ready (MAXWAIT is 60 seconds). Feb 16 08:56:16 debian systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Feb 16 08:56:16 debian systemd[1]: networking.service: Failed with result 'exit-code'. Feb 16 08:56:16 debian systemd[1]: Failed to start Raise network interfaces. Feb 16 08:56:16.113716 debian systemd-udevd[387]: Using default interface naming scheme 'v240'. Feb 16 08:56:16.113796 debian systemd-udevd[387]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Feb 16 08:56:16.113851 debian systemd-udevd[387]: Could not generate persistent MAC address for br0: No such file or directory Feb 16 08:56:16.115750 debian kernel: bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this Feb 16 08:56:16.115828 debian kernel: br0: port 1(eth0) entered blocking state Feb 16 08:56:16.115875 debian kernel: br0: port 1(eth0) entered disabled state Feb 16 08:56:16.115929 debian kernel: device eth0 entered promiscuous mode Feb 16 08:56:16.119800 debian kernel: r8169 :02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-2.fw Feb 16 08:56:16.120198 debian kernel: Generic PHY r8169-200:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE) Feb 16 08:56:16.251795 debian kernel: br0: port 2(eth1) entered blocking state Feb 16 08:56:16.251990 debian kernel: br0: port 2(eth1) entered disabled state Feb 16 08:56:16.391879 debian kernel: br0: port 1(eth0) entered blocking state Feb 16 08:56:16.391913 debian kernel: br0: port 1(eth0) entered forwarding state Feb 16 08:56:16.516862 debian systemd[1]: Starting Hostname Service... Feb 16 08:56:16.539520 debian systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Feb 16 08:56:16.539612 debian systemd[1]: networking.service: Failed with result 'exit-code'. Feb 16 08:56:16.539994 debian systemd[1]: Failed to start Raise network interfaces. Feb 16 08:56:16.671750 debian kernel: br0: port 3(wlan0) entered blocking state Feb 16 08:56:16.671808 debian kernel: br0: port 3(wlan0) entered disabled state Feb 16 08:56:16.671844 debian kernel: device wlan0 entered promiscuous mode Feb 16 08:56:16.671878 debian kernel: br0: port 3(wlan0) entered blocking state Feb 16 08:56:16.671912 debian kernel: br0: port 3(wlan0) entered forwarding state Feb 16 08:56:16.683579 debian hostapd[879]: wlan0: interface state UNINITIALIZED->ENABLED Feb 16 08:56:16.683579 debian hostapd[879]: wlan0: AP-ENABLED Any ideas where can I take a look? Thanks in advance! -- With best regards, Dmitry
binfmt-support cannot start at boot time because /var is not mounted
Dear Debian users, I am stuck with the following problem which I failed to debug on my Debian 10.3. In my setup I have /var as mounted volume: === /etc/fatab === UUID=83a3cb60-3334-4d11-9fdf-70b8e8703167/varbtrfs noatime,nodev,nosuid,subvol=var === end === Unfortunately sometimes I notice that binfmt-support is tried to be started "before" /var is mounted. Once I login and restart the service (I don't mount and/or repair anything), it starts just fine. === console === root@debian:~ # systemctl status binfmt-support * binfmt-support.service - Enable support for additional executable binary formats Loaded: loaded (/lib/systemd/system/binfmt-support.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-05-10 21:54:27 CEST; 10h ago Docs: man:update-binfmts(8) Process: 353 ExecStart=/usr/sbin/update-binfmts --enable (code=exited, status=2) Main PID: 353 (code=exited, status=2) May 10 21:54:27 debian update-binfmts[353]: update-binfmts: unable to open /var/lib/binfmts: No such file or directory root@debian:~ # ll /var/lib/binfmts total 16 drwxr-xr-x 1 root root 50 Mar 17 23:46 . drwxr-xr-x 1 root root 988 Mar 2 01:57 .. -rw-r--r-- 1 root root 49 Apr 14 2019 jar -rw-r--r-- 1 root root 59 Mar 17 23:46 python3.7 root@debian:~ # systemctl start binfmt-support root@debian:~ # systemctl status binfmt-support * binfmt-support.service - Enable support for additional executable binary formats Loaded: loaded (/lib/systemd/system/binfmt-support.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2020-05-11 09:01:04 CEST; 4s ago Docs: man:update-binfmts(8) Process: 9683 ExecStart=/usr/sbin/update-binfmts --enable (code=exited, status=0/SUCCESS) Main PID: 9683 (code=exited, status=0/SUCCESS) May 11 09:01:04 debian systemd[1]: Starting Enable support for additional executable binary formats... May 11 09:01:04 debian systemd[1]: Started Enable support for additional executable binary formats. root@debian:~ # dpkg -l | grep -i systemd ii systemd 241-7~deb10u3 amd64 system and service manager ... === end === One time the system was started with even more units failed because of inaccessible /var. There is nothing special in these units, and I haven't modified any *.service files. In other words the problem is floating, as number of failed unit varies from boot to boot. The difficulty is that I don't know how to debug system start / systemd at such early stage of system boot. Any help is appreciated. -- With best regards, Dmitry
Re: binfmt-support cannot start at boot time because /var is not mounted
On 2020-05-11 20:11, Darac Marjal wrote: > On 11/05/2020 08:40, Reco wrote: >> Hi. >> >> On Mon, May 11, 2020 at 09:33:59AM +0200, Dmitry Katsubo wrote: >> >>> root@debian:~ # systemctl status binfmt-support >>> * binfmt-support.service - Enable support for additional executable binary >>> formats >>>Loaded: loaded (/lib/systemd/system/binfmt-support.service; enabled; >>> vendor preset: enabled) >>>Active: failed (Result: exit-code) since Sun 2020-05-10 21:54:27 CEST; >>> 10h ago >>> Docs: man:update-binfmts(8) >>> Process: 353 ExecStart=/usr/sbin/update-binfmts --enable (code=exited, >>> status=2) >>> Main PID: 353 (code=exited, status=2) >>> >>> May 10 21:54:27 debian update-binfmts[353]: update-binfmts: unable to open >>> /var/lib/binfmts: No such file or directory >>> >>> Any help is appreciated. >> This should help your problem: >> >> mkdir /etc/systemd/system/binfmt-support.service.d >> >> cat > /etc/systemd/system/binfmt-support.service.d/override.conf << EOF >> [Unit] >> RequiresMountsFor=/var >> EOF > > As another alternative, one can run "systemctl edit > binfmt-support.service", which will create the intervening folders and > files for you, and reload the daemon if the editor exits with success. Thanks for suggestion! I have tried the advise and it actually worked (I will keep an eye on that because one reboot may not be representative). I wonder nevertheless what is the problem with this specific unit? It has dependency on local-fs.target which in turn should mount /var. So what exactly went wrong? -- With best regards, Dmitry
Re: binfmt-support cannot start at boot time because /var is not mounted
On 2020-05-11 20:11, Darac Marjal wrote: > On 11/05/2020 08:40, Reco wrote: >> Hi. >> >> On Mon, May 11, 2020 at 09:33:59AM +0200, Dmitry Katsubo wrote: >> >>> root@debian:~ # systemctl status binfmt-support >>> * binfmt-support.service - Enable support for additional executable binary >>> formats >>>Loaded: loaded (/lib/systemd/system/binfmt-support.service; enabled; >>> vendor preset: enabled) >>>Active: failed (Result: exit-code) since Sun 2020-05-10 21:54:27 CEST; >>> 10h ago >>> Docs: man:update-binfmts(8) >>> Process: 353 ExecStart=/usr/sbin/update-binfmts --enable (code=exited, >>> status=2) >>> Main PID: 353 (code=exited, status=2) >>> >>> May 10 21:54:27 debian update-binfmts[353]: update-binfmts: unable to open >>> /var/lib/binfmts: No such file or directory >>> >>> Any help is appreciated. >> This should help your problem: >> >> mkdir /etc/systemd/system/binfmt-support.service.d >> >> cat > /etc/systemd/system/binfmt-support.service.d/override.conf << EOF >> [Unit] >> RequiresMountsFor=/var >> EOF > > As another alternative, one can run "systemctl edit > binfmt-support.service", which will create the intervening folders and > files for you, and reload the daemon if the editor exits with success. Thanks for suggestion! I have tried the advise and it actually worked (I will keep an eye on that because one reboot may not be representative). I wonder nevertheless what is the problem with this specific unit? It has dependency on local-fs.target which in turn should mount /var. So what exactly went wrong? -- With best regards, Dmitry
Re: Some services cannot start at boot time because /run or /var is not mounted
Dear Debian community, I hit the similar problem but this time with /run folder. Few services have failed to start: # systemctl status php7.0-fpm.service Jun 24 23:09:48 debian php-fpm7.0[893]: [24-Jun-2020 23:09:48] ERROR: unable to bind listening socket for address '/run/php/php7.0-fpm.sock': No such file or directory (2) Jun 24 23:09:48 debian php-fpm7.0[893]: [24-Jun-2020 23:09:48] ERROR: FPM initialization failed Jun 24 23:09:48 debian systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/CONFIG Jun 24 23:09:48 debian systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'. Jun 24 23:09:48 debian systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager. # systemctl status motioneye.service Jun 24 23:09:47 debian systemd[1]: Started motionEye Server. Jun 24 23:09:48 debian meyectl[895]: INFO: hello! this is motionEye server 0.41 Jun 24 23:09:48 debian meyectl[895]: CRITICAL: pid directory "/run/motioneye" does not exist or is not writable Jun 24 23:09:48 debian systemd[1]: motioneye.service: Main process exited, code=exited, status=255/EXCEPTION Jun 24 23:09:48 debian systemd[1]: motioneye.service: Failed with result 'exit-code'. # cat /etc/tmpfiles.d/php.conf d /run/php/sessions 1733 root root # cat /etc/tmpfiles.d/motioneye.conf d /run/motioneye 0750 motion motion Just after the boot I have inspected /run folder. It was created/mounted correctly and there have been a lot of files/directories there. I suspect that all services that have created the necessary directory under /run were able to start normally. Few of them which relied on existence of specific directory, have failed to started. After I have replayed the corresponding instructions for tmpfiles.d, the services have started normally. I have a feeling that systemd-tmpfiles was executed before /run was mounted. Needless to note that the problem is not persistent: sometimes OS boots without a single failed service. How can I debug the problem? Thank you! On 2020-05-18 02:39, Dmitry Katsubo wrote: > On 2020-05-11 20:11, Darac Marjal wrote: >> On 11/05/2020 08:40, Reco wrote: >>> Hi. >>> >>> On Mon, May 11, 2020 at 09:33:59AM +0200, Dmitry Katsubo wrote: >>> >>>> root@debian:~ # systemctl status binfmt-support >>>> * binfmt-support.service - Enable support for additional executable >>>> binary formats >>>>Loaded: loaded (/lib/systemd/system/binfmt-support.service; enabled; >>>> vendor preset: enabled) >>>>Active: failed (Result: exit-code) since Sun 2020-05-10 21:54:27 CEST; >>>> 10h ago >>>> Docs: man:update-binfmts(8) >>>> Process: 353 ExecStart=/usr/sbin/update-binfmts --enable (code=exited, >>>> status=2) >>>> Main PID: 353 (code=exited, status=2) >>>> >>>> May 10 21:54:27 debian update-binfmts[353]: update-binfmts: unable to open >>>> /var/lib/binfmts: No such file or directory >>>> >>>> Any help is appreciated. >>> This should help your problem: >>> >>> mkdir /etc/systemd/system/binfmt-support.service.d >>> >>> cat > /etc/systemd/system/binfmt-support.service.d/override.conf << EOF >>> [Unit] >>> RequiresMountsFor=/var >>> EOF >> >> As another alternative, one can run "systemctl edit >> binfmt-support.service", which will create the intervening folders and >> files for you, and reload the daemon if the editor exits with success. > > Thanks for suggestion! I have tried the advise and it actually worked > (I will keep an eye on that because one reboot may not be representative). > I wonder nevertheless what is the problem with this specific unit? It has > dependency on local-fs.target which in turn should mount /var. So what > exactly went wrong? -- With best regards, Dmitry
Re: /dev/dvb do not exist
On 2022-09-21 19:59, Thierry Leurent wrote: > Hello, > > I'm trying to configure an FM/DAB/DVB stick, it's an r820t using an rtl2838 > chip. > I'm able to listen fm radios. > When I use w_scan, it is not able to find the folder /dev/dvb. > > How can I create this ? > > Thanks > > Thierry Hello, How do you perform the channel scanning? E.g. * Install [dvb-apps](http://packages.debian.org/dvb-apps) and perform the channel scanning: $ scan /usr/share/dvb/dvb-t/nl-All > channels.conf You will see among other staff something like this: >>> tune to: >>> 72200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_1_2:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE 0x 0x044d: pmt_pid 0x1b62 Digitenne -- Nederland 1 (running) 0x 0x044e: pmt_pid 0x1b6c Digitenne -- Nederland 2 (running) 0x 0x044f: pmt_pid 0x1b76 Digitenne -- Nederland 3 (running) 0x 0x0450: pmt_pid 0x1b80 Digitenne -- TV West (running) 0x 0x0457: pmt_pid 0x1bc6 Digitenne -- Radio West (running) 0x 0x0458: pmt_pid 0x1bd0 Digitenne -- Radio 1 (running) 0x 0x0459: pmt_pid 0x1bda Digitenne -- Radio 2 (running) 0x 0x045a: pmt_pid 0x1be4 Digitenne -- 3FM (running) 0x 0x045b: pmt_pid 0x1bee Digitenne -- Radio 4 (running) 0x 0x045c: pmt_pid 0x1bf8 Digitenne -- Radio 5 (running) 0x 0x045d: pmt_pid 0x1c02 Digitenne -- Radio 6 (running) 0x 0x045f: pmt_pid 0x1c16 Digitenne -- FunX (running) Network Name 'Digitenne' * Install any player that supports DVB on your wish (Xine, mplayer, Xawtv, Me TV7). For e.g. xine and mplayer copy the scanned channels information to ~/.xine/channels.conf and ~/.mplayer/channels.conf correspondingly. Launch the player: $ xine "dvb://Nederland 1" * Enjoy :) -- With best regards, Dmitry
Allocate tty1 for kernel messages
Dear Debian users, I am trying to make a following setup on Debian bullseye: * tty1 is used to display kernel messages only * tty[2-5] are allocated for login I have modified /etc/default/console-setup so that it reads: ACTIVE_CONSOLES="/dev/tty[2-5]" and rebooted. What I observe is that tty1 displays kernel messages during the boot (OK) but also ends with an invitation for login on tty1 (WRONG). How can I force that tty1 is not used for login? Thanks in advance. Similar topics: * https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1789170 * https://forum.proxmox.com/threads/newb-question-console-setup-tty-changed-but-not-taking-effect.83368/ * https://unix.stackexchange.com/questions/198791/how-do-i-permanently-change-the-console-tty-font-type-so-it-holds-after-reboot -- With best regards, Dmitry
Re: Allocate tty1 for kernel messages
On 2022-09-25 17:52, basti wrote: > Am 25.09.22 um 17:25 schrieb David Wright: >> On Sun 25 Sep 2022 at 17:01:23 (+0200), Dmitry Katsubo wrote: >>> I am trying to make a following setup on Debian bullseye: >>> >>> * tty1 is used to display kernel messages only >>> * tty[2-5] are allocated for login >>> >>> I have modified /etc/default/console-setup so that it reads: >>> >>> ACTIVE_CONSOLES="/dev/tty[2-5]" >>> >>> and rebooted. What I observe is that tty1 displays kernel messages during >>> the boot (OK) but also ends with an invitation for login on tty1 (WRONG). >>> >>> How can I force that tty1 is not used for login? >> >> I think you still need to run: >> >> # dpkg-reconfigure console-setup >> >> to get that variable enacted. Then check that the file >> /etc/console-setup/cached_setup_keyboard.sh, which AIUI >> is what does the work, has been modified. >> >> That's similar for a lot of configuration parameters >> in /etc/default/. David, thanks for your input. I have run "dpkg-reconfigure console-setup" and rebooted and it didn't help. > Hello, > > first of all disable login on tty1: > > systemctl disable getty@tty1.service I have disabled and stopped this service: # systemctl status getty@tty1.service ● getty@tty1.service - Getty on tty1 Loaded: loaded (/lib/systemd/system/getty@.service; disabled; vendor preset: enabled) Drop-In: /etc/systemd/system/getty@.service.d └─noclear.conf Active: inactive (dead) Docs: man:agetty(8) man:systemd-getty-generator(8) http://0pointer.de/blog/projects/serial-console.html Sep 26 00:10:34 debian systemd[1]: Started Getty on tty1. Sep 26 01:20:43 debian systemd[1]: Stopping Getty on tty1... Sep 26 01:20:43 debian systemd[1]: getty@tty1.service: Succeeded. Sep 26 01:20:43 debian systemd[1]: Stopped Getty on tty1. I believe after that the "login:" prompt should disappear from tty1, but it didn't. Should I reboot to make this setting active? > Then in /etc/systemd/journald.conf: > (or in one of the conf.d folders, see man journald.conf.d) > > ForwardToConsole=yes > TTYPath=/dev/tty1 > > Will do it. That will forward kernel messages to tty1, right? -- With best regards, Dmitry
Re: zoneminder in experimental
On Sunday, 13 January 2019 12:14:26 AM AEDT Rainer Dorsch wrote: > I just saw you manage an incredible amount of Debian packages: > > https://qa.debian.org/developer.php?email=onlyjob%40debian.org Well, I did some work on all those packages some time ago but now they do not receive the same amount of attention... > Many thanks for that. While looking through the list, I discovered > brainparty, which I did not know before. Thank you. Brainparty is awesome but I did not hear from upstream in years. Project appears to be dormant but the package still works well (at least last time I tried it). > I am using zoneminder here in stretch. I saw you uploaded several new > versions 1.32.x to experimental. I am just wondering if you intend to > upload a new version to sid before the release of buster or do the > versions 1.32.x have severe limitations over the version 1.30.4 which is > currently in sid and buster? Current blocker is this: https://github.com/ZoneMinder/zoneminder/issues/2220 I hope that the next release might be good enough for "unstable" and then it shouldn't take too long until it propagates to "testing" hopefully. -- Best wishes, Dmitry Smirnov. --- Truth — Something somehow discreditable to someone. -- H. L. Mencken, 1949 signature.asc Description: This is a digitally signed message part.
Core dumps are instantly removed
Dear Debian users, Hopefully you can easily help me with my confusion. I would like to collect / keep core dumps in the system. For that I use systemd-coredump package which is configured as following: === cut /etc/systemd/coredump.conf === [Coredump] Storage=external MaxUse=5G === cut === Then I have created a script to send core dump report daily to root: === cut /etc/cron.daily/coredump === YESTERDAY=`date --date="1 day ago" +%Y-%m-%d` MESSAGE=`coredumpctl list --no-pager -r -S $YESTERDAY -U $(date +%Y-%m-%d) 2> /dev/null` && (echo "$MESSAGE"; echo -e "\nLast core dump info:\n"; coredumpctl info --no-pager; echo -e "\nCore dumps:\n"; ls -l /var/lib/systemd/coredump; ) | mail -s "Core dumps created yesterday $YESTERDAY" root === cut === What I get is: === cut === TIMEPID UID GID SIG COREFILE EXE Tue 2019-12-10 11:27:26 CET2537 1003 100 5 missing /usr/bin/light-locker Last core dump info: PID: 2537 (light-locker) ... Signal: 5 (TRAP) Timestamp: Tue 2019-12-10 11:27:25 CET (20h ago) Command Line: light-locker Executable: /usr/bin/light-locker ... Storage: /var/lib/systemd/coredump/core.light-locker.1003.810304...157597364500.lz4 (inaccessible) Message: Process 2537 (light-locker) of user 1003 dumped core. Stack trace of thread 2537: #0 0x7fde22515c75 n/a (libglib-2.0.so.0) #1 0x7fde22516d0d g_log_default_handler (libglib-2.0.so.0) #2 0x7fde22516f5f g_logv (libglib-2.0.so.0) #3 0x7fde2251714f g_log (libglib-2.0.so.0) #4 0x563b0e2f30a3 n/a (light-locker) #5 0x7fde22615107 g_type_create_instance (libgobject-2.0.so.0) ... Core dumps: total 0 === cut === As one can see, stack trace is somehow captured by coredumpctl (where it gets it from?) but core file is not there. I would like core dump files to be preserved for (say) 10 days. light-locker generates really tiny core dump when I start it from console: === cut === $ /usr/bin/light-locker Trace/breakpoint trap (core dumped) # ls -l /var/lib/systemd/coredump/ -rw-r-+ 1 root root 884992 Dec 13 14:16 core.light-locker.1003.8103...157624301300.lz4 === cut === Also I am aware about this setting: === cut /usr/lib/tmpfiles.d/systemd.conf === d /var/lib/systemd/coredump 0755 root root 3d === cut === but it configures the directory to be cleaned in three days while they are removed sooner. Any ideas? Thanks in advance! P.S. I have read: https://wiki.debian.org/HowToGetABacktrace#Core_dump https://wiki.archlinux.org/index.php/Core_dump but didn't find the answer. -- With best regards, Dmitry
Core dumps are instantly removed
Dear Debian users, Hopefully you can easily help me with my confusion. I would like to collect / keep core dumps in the system. For that I use systemd-coredump package which is configured as following: === cut /etc/systemd/coredump.conf === [Coredump] Storage=external MaxUse=5G === cut === Then I have created a script to send core dump report daily to root: === cut /etc/cron.daily/coredump === YESTERDAY=`date --date="1 day ago" +%Y-%m-%d` MESSAGE=`coredumpctl list --no-pager -r -S $YESTERDAY -U $(date +%Y-%m-%d) 2> /dev/null` && (echo "$MESSAGE"; echo -e "\nLast core dump info:\n"; coredumpctl info --no-pager; echo -e "\nCore dumps:\n"; ls -l /var/lib/systemd/coredump; ) | mail -s "Core dumps created yesterday $YESTERDAY" root === cut === What I get is: === cut === TIMEPID UID GID SIG COREFILE EXE Tue 2019-12-10 11:27:26 CET2537 1003 100 5 missing /usr/bin/light-locker Last core dump info: PID: 2537 (light-locker) ... Signal: 5 (TRAP) Timestamp: Tue 2019-12-10 11:27:25 CET (20h ago) Command Line: light-locker Executable: /usr/bin/light-locker ... Storage: /var/lib/systemd/coredump/core.light-locker.1003.810304...157597364500.lz4 (inaccessible) Message: Process 2537 (light-locker) of user 1003 dumped core. Stack trace of thread 2537: #0 0x7fde22515c75 n/a (libglib-2.0.so.0) #1 0x7fde22516d0d g_log_default_handler (libglib-2.0.so.0) #2 0x7fde22516f5f g_logv (libglib-2.0.so.0) #3 0x7fde2251714f g_log (libglib-2.0.so.0) #4 0x563b0e2f30a3 n/a (light-locker) #5 0x7fde22615107 g_type_create_instance (libgobject-2.0.so.0) ... Core dumps: total 0 === cut === As one can see, stack trace is somehow captured by coredumpctl (where it gets it from?) but core file is not there. I would like core dump files to be preserved for (say) 10 days. light-locker generates really tiny core dump when I start it from console: === cut === $ /usr/bin/light-locker Trace/breakpoint trap (core dumped) # ls -l /var/lib/systemd/coredump/ -rw-r-+ 1 root root 884992 Dec 13 14:16 core.light-locker.1003.8103...157624301300.lz4 === cut === Also I am aware about this setting: === cut /usr/lib/tmpfiles.d/systemd.conf === d /var/lib/systemd/coredump 0755 root root 3d === cut === but it configures the directory to be cleaned in three days while they are removed sooner. Any ideas? Thanks in advance! P.S. I have read: https://wiki.debian.org/HowToGetABacktrace#Core_dump https://wiki.archlinux.org/index.php/Core_dump but didn't find the answer. -- With best regards, Dmitry
How to properly close a false bug report?
Hi. I submitted a bug report #393779: libglademm-2.4-1c2a: fails to load .glade file. Later I've found that the problem was on my side. I've added a note to the report. How to close the bug properly in this case? As I understand I can send a mail [EMAIL PROTECTED] to tag the report as wontfix and close it. Is this the right way? Please add me to CC as I'm not subscribed to debian-user list. Regards, Dmitry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to properly close a false bug report?
Thanks for your answers! I've already sent an email saying that was my problem. I hope the maintainer will close the bug. Regards, Dmitry Martin Zobel-Helas wrote: On Thu Oct 26, 2006 at 17:48:07 -0500, Ron Johnson wrote: On 10/26/06 17:09, Dmitry Kurochkin wrote: Hi. I submitted a bug report #393779: libglademm-2.4-1c2a: fails to load .glade file. Later I've found that the problem was on my side. I've added a note to the report. How to close the bug properly in this case? As I understand I can send a mail [EMAIL PROTECTED] to tag the report as wontfix and close it. Is this the right way? Please add me to CC as I'm not subscribed to debian-user list. You count send an email to [EMAIL PROTECTED] saying, "never mind, my fault". The maintainer will (hopefully) see it and close it. mail [EMAIL PROTECTED] and state that it was a problem on your side. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
pam bug
OS: debian etch I have a large group. More 1000 users. Linux PAM not apply /security/limits.conf for some users. in small group all work fine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
how to contribute package to repository
Dear sirs, Our company is software developer. Our software is proprietary RDF database. We would like to include our software package in the official Linux distribution repository. What do we need for this? A special license? Should we open source codes? Best regards, Dmitry Head of Department system administration -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/feab82ff91a3504d9bbaf7f223f861460258cfee8...@fs03.avicomp.com
KDE's Applications Launcher Menu incorrect behavior
Hello! I noticed an incorrect behavior of the KDE's Applications Launcher Menu in Debian: not all characters are printed when i type something in search field. For example, I type "kate", but "kte" has printed. Sometimes only first symbol has printed. The same behavior is in Discover application. In other applications all works correctly. It began when I have started to use standard system keyboard layouts instead of IBus. What should I do to collect more details of the incorrect behavior to help to fix it? P.S.: Debian 9 AMD64 KDE.
Networking with 'allow-hotplug' had broken after upgrading systemd 215-17+deb8u5 up to +deb8u6
Hello. /etc/network/interfaces - as usual: "allow-hotplug eth0", "iface eth0 inet dhcp" Systemd upgraded from 215-17+deb8u5 up to 215-17+deb8u6 The system hangs for 1m30s during boot up, network interface is down, but can be ifup'ed manually. Reverting ifup@.service back to deb8u5 solves the problem: diff -u ./systemd-8u6/ifup@.service ./systemd-8u5/ifup@.service --- ./systemd-8u6/ifup@.service 2016-12-21 23:33:51.0 +0300 +++ ./systemd-8u5/ifup@.service 2016-07-24 19:55:54.0 +0300 @@ -1,9 +1,8 @@ [Unit] Description=ifup for %I -After=local-fs.target network-pre.target networking.service systemd-sysctl.service +After=local-fs.target network-pre.target networking.service Before=network.target BindsTo=sys-subsystem-net-devices-%i.device -After=sys-subsystem-net-devices-%i.device ConditionPathIsDirectory=/run/network DefaultDependencies=no -- Best regards, Dmitrymailto:sidorov.slom...@gmail.com
no keyboard layouts after upgrade
Hi everyone! I updated my Debian 7 and got lots of problems. The biggest one for now is that I don't have any way to switch the keyboard layouts. gnome-control-center was removed during dist-upgrade so I had to reinstall it manually. Now I set two input sources there (Russian + English), but there is no menuitem Layouts in Keyboard->Shortcuts. I found a "switch to next input source", it says Shift+Space, but does not work at all. root@# cat /etc/issue Debian GNU/Linux 8 \n \l root@# cat /etc/debian_version 8.1 Thanks for your help. -- С уважением, Дмитрий А. Зворыкин -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJ--P9jpcQt4Bcu5djM5gVCxCab-=uzxtomovoxrvivtimu...@mail.gmail.com
Re: Merge Extra free space into current linux partition
"partprobe" can be useful in order to reread partition table. In fact it is always good to use thic command after partitioning. example: sudo partprobe /dev/sda D. > On Fri, Oct 23, 2009 at 12:08:15AM -0700, Kushal Koolwal wrote: > > > Does anybody else know if > > there is a way to reread the partion table an a running system? > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
need help with installing WLAN package
Hi, i recently install debian sarge and right now I am trying to configure it to work with wireless USB adaptor 'netgear ma101'. I downloaded the linux-wlan-ng-0.2.3.tar.gz uncompressed it and then tried to 'make config' it however it complaned that i don't have configed kernel. Instruction that come in the package README file say that I need to have "configured kernel source code for the kernel I am running". I installed debian sarge from binaries and since i am very inexperienced in linux I have no idea how to provide configured kernel code or is there an alternate way? Any help will be greatly appreciated. best regards, Dmitry Hits.
Distributed ldap-based mail system
Hello! I'd like to hear any thoughts how to deploy mail system in many offices, but with a single corporate address book and a single public key infrastructure. Perhaps, somebody wants to share his experience or has comments for my project ( http://www.rojkov.spb.ru/eng/projects ). Just because I don't want to invent a wheel again... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SUBSCRIBE
Sergey A. Ovchar wrote: Hello , ËÏÇÄÁ ÚÁÈÏÞÅÛØ "ÏÔÐÉÓÁÃÁ" man procamil ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
woody reiserfs
Hi gents, I wonder, if woody offers reiserfs/xfs/etx2 installation? Thnx. --- Ciao, Dmitry
Debian lifecycle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everybody, I'm not subscribed to the list, so please CC me in your response. My question is about release lifecycle in Debian world: exactly how long on average "stable" release is supported after it became "obsolete" or in other words when there's new "stable" release? (as example - how long woody would be supported in terms of errata etc. after sarge goes live?) Or if old "stable" release "dies" after new is out - how one performes upgrade etc (I know about apt-get but I guess there's something more involved in this process) - -- Dmitry Makovey Web Systems Administrator Athabasca University (780) 675-6245 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAhUMIyDrVuGfS98QRAhZKAJ4ou1kCyHDhbpQttBQyggWnY9G3RgCgp+6X 1c812TOQJ4v+a9k7TjcgU8o= =DUFn -END PGP SIGNATURE-
Re: Debian lifecycle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First of all thanks everybody for prompt replies. I see the picture now and it makes me feel good :) So it looks like after deployment of freshly-released "stable" I have about 2 years in average to sleep well without dreaming of upgrades. After that I silently get latest "stable" from repository using, let's say, apt-get, tune/configure system and I'm done for next 2 years rough. Which seems to be a good lifecycle in comparison to, for example, fedora with stated lifecycle 6 month. Please correct me if I'm wrong with my assumptions. On April 20, 2004 11:13 am, Florian Ernst wrote: > Quoting from http://www.debian.org/security/faq#lifespan : > "The security team tries to support a stable distribution for about > one year after the next stable distribution has been released, except > when another stable distribution is released within this year. It is > not possible to support three distributions; supporting two > simultaneously is already difficult enough." Thanks, I somehow missed that part of documentation. > The stable release before Woody, called Potato, has been supported > until June 30th, 2003 which was actually a little bit less than one > year after the release of Woody on July 19, 2002. that's usefull statistics. Really good number for commercial/enterprise deployment of Debian (3+ would be even better but 2 is good enough :) ) > > Or if old "stable" release "dies" after new is out - how one performes > > upgrade etc (I know about apt-get but I guess there's something more > > involved in this process) > > There are numerous update procedures. The Release Notes of the new > release will list the recommended way. Please see > http://www.debian.org/releases/woody/i386/release-notes/ch-upgrading > for an example. thanks again for valuable responses everybody and thanks for pointer to related documents. - -- Dmitry Makovey Web Systems Administrator Athabasca University (780) 675-6245 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAhWimyDrVuGfS98QRAloJAKDEV0vuxVpML0yw2aGUStdA/TWUkACgnLJX l7JXp8fvRfeylFRRS7AvL+o= =7WQa -END PGP SIGNATURE-