Re: File check at boot
2015-07-21 18:28 GMT+02:00 Martin Skjöldebrand : > > Quoting Erick Ocrospoma : > > And the only half helpful suggestion from the hosting was running in single > mode from grub, but the disk is mounted at that time. Else to rollback a > snapshot of the server which would mean hours of reconfiguration which I am > hoping to avoid. It may be possible to run fsck in single mode. Remount the root partition in read-only mode: mount -o remount,ro / If it fails due to open files, find the daemons opening files for writing on the root partition and terminate them (or kill -9 if necessary). Lsof may help you find what daemon has open files but last time I tried, it was simpler to run ps aux and kill what obviously was a logger of some sort and it was enough to remount the partition in read only mode. Then run fsck. Frederic -- 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/caj7r-8qfuwagpxwuxalvajbj7r0imn3gby7-i8t7auj412m...@mail.gmail.com
No sound in Debian 8 'jessie' Xfce on Youtube
Hi, I have had problems with Debian 8 'jessie' Xfce edition. I didn't get any sound initially. Then after 'some' configuration, I got sound working. But sound related problems were still there. When I plug-in the headphone I got no sound. Then I have to re-adjust using 'pavucontrol' and 'alsamixer'. And the main problem was with Youtube videos. I thought that was because I don't have Flash player installed and I don't want to. But then I tried Debian jessie GNOME and everything was working fine. Even the Youtube video's sound. So what's the deal with Xfce? Why there was no sound on YouTube? And why I had to configure every time I switch from and to headphone and speaker? With thanks, Muntasim Ul Haque -- 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/55ae63cd.6080...@inventati.org
Re: File check at boot
Quoting Jape Person : Not sure this will be at all helpful considering that the consensus seems to be that fsck is probably not what you need right now. I just wanted to be sure that you got some sort of answer regarding the running of systemd-fsck. You should be able to see the result of an fsck run with $ cat /run/initramfs/fsck.log I use # tune2fs -c -1 /dev/sda1 to set the system to prevent a full fsck from running at boot time and # tune2fs -c 1 /dev/sda1 to cause the system to force a full fsck during the next boot. Ah brilliant, thanks. I notice a few line like /dev/vda1: Clearing orphaned inode 94755 (uid=106, gid=111, mode=0100600, size=0) /dev/vda1: Clearing orphaned inode 90459 (uid=106, gid=111, mode=0100600, size=0) but I really can't see this causing catastrophic server crashes if unfixed. /Martin S -- * *** This address is for technical maillists only*** *** Please use my primary mail address at the .org domain*** *** for all other matters*** * -- 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/20150722032217.horde.ygrmaj13tjleehglec9z...@www.skjoldebrand.eu
Re: Wireless disabled in Debian after MacOS use (stuck)
On 7/21/2015 5:04 PM, Michael Bonert wrote: I solved the problem! I was reading the Network Manager how to -- that is found here: https://wiki.debian.org/NetworkManager This is what I did: ** # vi /etc/NetworkManager/NetworkManager.conf -IT WAS [ifupdown] managed=false -CHANGED TO [ifupdown] managed=true --- # /etc/init.d/network-manager restart ** I am still baffled about why this happened. It doesn't make sense to me! Any how, I hope if someone else encounters wireless problems with the Broadcom driver ( b43 ) ... my list of things to try ( https://lists.debian.org/debian-user/2015/07/msg00947.html ) is useful. Michael Do you have the card set up in /etc/network/interfaces ? In theory, the managed setting of network manager should only make a difference if there is configuration in /etc/network/interfaces for the interface in question. Later, Seeker -- 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/55aefa81.3010...@comcast.net
Re: mplayer "Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file"
I managed to solve this with the help of the people on gmane.comp.video.mplayer.user - with the option '-vo xv' to mplayer (mplayer1) the error message disappears with no loss of functionality or undesired side-effects to it. -- underground experts united http://user.it.uu.se/~embe8573 -- 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/87k2ttm3y2@nl106-137-147.student.uu.se
Wireless disabled in Debian after MacOS use (stuck)
I solved the problem! I was reading the Network Manager how to -- that is found here: https://wiki.debian.org/NetworkManager This is what I did: ** # vi /etc/NetworkManager/NetworkManager.conf -IT WAS [ifupdown] managed=false -CHANGED TO [ifupdown] managed=true --- # /etc/init.d/network-manager restart ** I am still baffled about why this happened. It doesn't make sense to me! Any how, I hope if someone else encounters wireless problems with the Broadcom driver ( b43 ) ... my list of things to try ( https://lists.debian.org/debian-user/2015/07/msg00947.html ) is useful. Michael -- 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/20150721200416.fw2bl24s0sc8s...@webmail.utoronto.ca
Re: auto-mount NFS shares on boot
Hi, On 07/16/2015 09:04 AM, n n wrote: > trying to mount nfs-shares at boot I have exactly the problem mentioned by > Christian: > (in Message-id: <558e8105.5030...@iwakd.de>) > >> - On some systems with static IP addresses (and >> /etc/network/interfaces), I had the problem that even though the >> interface was conisdered up and ready by the kernel, the switch it >> was connected to needed 30s or so to realize that fully (and >> packets were simply dropped beforehand). Since those systems also >> needed to mount NFS... > > Christian then recommends applying a unit he calls wait-for-nfs-server. > > My problem now is that if I apply that unit (or do other tricks like a sleep > in > /etc/network/interfaces the mounts are there after booting, but I have errors > like that in journalctl: > > Jul 14 16:07:02 hhh rpcbind[657]: Starting rpcbind daemon > Jul 14 16:07:02 hhh rpc.statd[681]: Version 1.2.8 starting > Jul 14 16:07:02 hhh rpc.statd[681]: Flags: TI-RPC > Jul 14 16:07:02 hhh rpc.statd[682]: Version 1.2.8 starting > Jul 14 16:07:02 hhh rpc.statd[682]: Flags: TI-RPC > Jul 14 16:07:02 hhh rpc.statd[683]: Version 1.2.8 starting > Jul 14 16:07:02 hhh sm-notify[684]: Version 1.2.8 starting > [...] > So, rpc.statd is there, but why with the --no-notify option? > > To me it looks like rpc.statd gets started multiple times (why?) and > that confuses me and the whole nfs mount process. Ok, so in your case you're also running into the same bug [1] of this very same thread, namely that remote filesystems are not ordered relative to nfs-common. In your case it's rpc.statd and not rpc.gssd, but the cause is the same. In your case, instead of mounts just failing, the mount.nfs binary has a weird logic in it that for NFSv2 and NFSv3 mounts, if statd isn't already running, it will call /usr/sbin/start-statd. That's a script (you can look at it) and it will start rpc.statd multiple times - with the --no-notify option. (Because statd notifications should only happen at boot, but mount.nfs isn't just called at boot.) The problem you have here is the following: - nfs-common tries to start statd regularly (without any options unless you specified them explicitly via /etc/default/nfs-common) - at the same time you apparently have multiple (!) nfs mounts for which mount.nfs is started - each of those mount.nfs processes tries to run statd with the --no-notify option - then they start getting it each other's way, at the end one wins all or all but one mounts (depending on which wins) will just fail The start-statd logic of mount.nfs is something that doesn't jibe well with systemd, since it was designed back when nfs mounts were not done in parallel but rather one after the other, so that even if it were executed at boot, it wouldn't have caused this issue, because boot was much more serialized. (Also, starting statd in systemd as part of a mount unit is not a good idea.) To solve your problem: Just apply the same workaround until it's fixed in Jessie: make sure that NFS mounts only happen after nfs-common is done, then mount.nfs will not try to start statd itself (because it's already running) and boot should work out. For this, create a directory /etc/systemd/system/nfs-common.service.d and then create a file /etc/systemd/system/nfs-common.service.d/remote-fs-pre.conf with the following contents: [Unit] Before=remote-fs-pre.target Then it should work. Regards, Christian [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775542 signature.asc Description: OpenPGP digital signature
Re: Kerberos-secured NFSv4: nss_getpwnam: name '8' does not map into domain
Hi there, On 07/10/2015 01:02 PM, Jonas Meurer wrote: > Am 2015-07-08 15:34, schrieb Jonas Meurer: >> I've another annoying issue with my new Kerberos-secured NFSv4 setup. >> Sometimes when Exim4 writes to the mounted NFS share, it fails to set >> owner and permissions on the written file. Exim4 runs as local user >> Debian-exim:Debian-exim but tries to set owner of created files on >> the NFS share to 'mail:mail'. Both the local user Debian-exim and >> the local user mail are authenticated against the Kerberos server and >> principals 'debian-e...@domain.org' as well as 'm...@domain.org' do >> exist. >> >> Obviously, not time Exim4 creates a file and sets owner on the NFS >> share, the error is produced. Most of the time, this just works and >> new files are owned by 'mail:mail'. But sometimes, it fails. In >> these cases, Exim4 gives the following error: > > In the meantime, I did some further debugging. I still have no clue > what triggers the error. It happens serveral times every hour, but > I didn't find a pattern yet. Interestingly, the error vanishs by > itself after a few minutes. > > Below's some debugging output of rpc.idmapd on the Kerberos-/NFS- > Server. Ok, these long entries explain what's happening from the server perspective - and the server does everything correct here. First of all, this has nothing do with Kerberos, but with NFSv4's idmapping. Let me back up a little. If you look at the internet standard covering NFSv4 (RFC 3530) [0], there's a nice little section called 5.8. Interpreting owner and owner_group which describes the attributes used to transmit user and group ownership information between server and client (both for what to show with 'ls' and for what to do with 'chown/chmod'). To quote parts of that section: [...] It is expected that the client and server will have their own local representation of owner and owner_group that is used for local storage or presentation to the end user. Therefore, it is expected that when these attributes are transferred between the client and server that the local representation is translated to a syntax of the form "user@dns_domain". This will allow for a client and server that do not use the same local representation the ability to translate to a common syntax that can be interpreted by both. [...] The translation used to interpret owner and group strings is not specified as part of the protocol. This allows various solutions to be employed. For example, a local translation table may be consulted that maps between a numeric id to the user@dns_domain syntax. [...] In the case where there is no translation available to the client or server, the attribute value must be constructed without the "@". Therefore, the absence of the @ from the owner or owner_group attribute signifies that no translation was available at the sender and that the receiver of the attribute should not use that string as a basis for translation into its own internal format. [...] Note that Linux always uses uids internally in the kernel to store user credentials, so what happens is that the sender of a NFSv4 packet takes the uid, translates it into a string representation containing an @, and then sends that over the netowrk - the receiver translates it back into a uid and uses that in its own data structures. (Btw. if you run ls to show a directory listing, ls will translate it back into a string representation, possibly a different one, so you may see a username instead of just a number. So on NFS three different translations will happen if you type ls -l somewhere: 1. server: uid -> nfs-name, 2. client (kernel): nfs-name -> uid and 3. client (ls): uid -> name. nfs-name is typically the same as name with just an @nfs4-domain at the end, but doesn't have to be.) This is what the idmapping on both the server and the client is about: to tell the NFSv4 server and client implementations how to do this type of translation. (Side note: if you are using sec=sys and a recent enough kernel on both server and client, IIRC 3.4 or newer - but I may be mistaken about the version that was properly implemented - idmapping is not required at all, since the kernel supports just sending the uids in ASCII as numbers in that field, see the RFC. But that doesn't work for sec=krb5*, because the security model depends on requests being authenticated with the principal of the user on the client, which implies that there needs to be idmapping anyway to map the ids to a principal and back. On the other hand, sec=sys doesn't have anything you'd want to call security model at all. sec=sys is just "let me trust the client completely" or at best "let me trust the client with everything but root itself".) Now let's get back to those log messages: > Jul 10 10:46:59 nfs1 rpc.idmapd[4946]: nfsdcb: authbuf=gss/krb5i authtype=user > Jul 10 10:46:59 nfs1 rpc.idmapd[4946]: nfs4_name_to_uid: calling > nsswitch->name_to_uid > Jul 10
Re: File check at boot
On 07/21/2015 12:28 PM, Martin Skjöldebrand wrote: Quoting Erick Ocrospoma : On 21 July 2015 at 10:32, Martin Skjöldebrand wrote: Hi, Mail from desperate user here: OS: Debian 8.1 Jessie Scenario: Mail/web server with file corruption. I have I/O errors on a few blocks which results in regular (daily) server crashes (including kernel panic) at random times during the day, usually afternoon CET. I need to run fsck on the disks. I have grub2 installed on the server. Catch: For some reason there is only one partition - yes I know this is retarded. Catch2: This is on virtual hosting provider so I can access the server through ssh or vnc but not physically How can I run fsck at boot time while the disks are umounted. Adding single to the grub linux kernel line fails to actually run fsck as the disk is mounted when server goes into rescue mode. I've Googled and (among other suggestions) read about the systemd fsck service but am not sure this will help or really how to invoke the thing properly Adding init=/bin/systemd fsck.mode=force fsck.repair=yes didn't seem to do much. Well, common fsck at boot procedure I ever used was: touch /forcefsck Thanks for suggestion. I've tried this but the server is back up in a few seconds, so I am fairly certain it isn't running a fsck at boot time after issuing "reboot". And the only half helpful suggestion from the hosting was running in single mode from grub, but the disk is mounted at that time. Else to rollback a snapshot of the server which would mean hours of reconfiguration which I am hoping to avoid. /Martin S Not sure this will be at all helpful considering that the consensus seems to be that fsck is probably not what you need right now. I just wanted to be sure that you got some sort of answer regarding the running of systemd-fsck. You should be able to see the result of an fsck run with $ cat /run/initramfs/fsck.log I use # tune2fs -c -1 /dev/sda1 to set the system to prevent a full fsck from running at boot time and # tune2fs -c 1 /dev/sda1 to cause the system to force a full fsck during the next boot. HTH, Jape -- 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/55aec915.5050...@comcast.net
Re: audio restore functionaility
On Mon, Jul 20, 2015 at 06:42:58PM +0100, Lisi Reisz wrote: > > But we don't really know much about what the OP did. We haven't heard from > him since his initial enquiry. He may not even be subscribed. -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X -- 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/20150721202121.GA9130@tal
Re: Debug files are given unreadable names
Am 21.07.2015 um 15:53 schrieb Shriramana Sharma: > Does such a script exist as of now? If not, could it please be > provided as you mention above? I don't know. You best follow-up at the bug report I quoted. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: File check at boot
On Tuesday 21 July 2015 20.31.07 Nicolas George wrote: > Le tridi 3 thermidor, an CCXXIII, Martin S a écrit : > > For what it's worth this is a mild example of the I/O error I get in > > connection with the crashes... > > > > https://www.dropbox.com/s/3ezm3jn272xpdmq/Selection_024.png > > Why a screenshot to copy text? > It's from a web based VNC session I can't copy from or paste to. And I was too lazy to open a writeable one. > That is a read error on the block device, not a corruption of the > filesystem: fsck will not really help you. I posted something the like to my hosting - we'll see what they say. Thanks for all replies so far =) /Martin S -- 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/2127351.PXOUVBSV3E@mobile-dragon
Re: File check at boot
Le tridi 3 thermidor, an CCXXIII, Martin S a écrit : > For what it's worth this is a mild example of the I/O error I get in > connection with the crashes... > > https://www.dropbox.com/s/3ezm3jn272xpdmq/Selection_024.png Why a screenshot to copy text? That is a read error on the block device, not a corruption of the filesystem: fsck will not really help you. Regards, -- Nicolas George signature.asc Description: Digital signature
Re: File check at boot
For what it's worth this is a mild example of the I/O error I get in connection with the crashes... https://www.dropbox.com/s/3ezm3jn272xpdmq/Selection_024.png /Martin S -- 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/1683299.JBY7sO58k2@mobile-dragon
Re: File check at boot
Quoting Martin Read : On 21/07/15 16:32, Martin Skjöldebrand wrote: Scenario: Mail/web server with file corruption. I have I/O errors on a few blocks which results in regular (daily) server crashes (including kernel panic) at random times during the day, usually afternoon CET. I need to run fsck on the disks. I have grub2 installed on the server. If you have "I/O errors on a few blocks", it seems to me that the hardware your virtual hosting provider uses to host your server is either defective, dying, or misconfigured, and you should address *that* as a matter of urgency. The systemd-fsck service *should* run automatically, as far as I can tell from casual inspection of the relevant systemd unit files, but if you are actually getting *I/O errors*, fsck is not going to save you. Thanks, I actually on one of the first calls said I saw OpenStack being mentioned in the kernel panic message so I actually wondered if it was my server or the hardware hosting the server. They (naturally) pointed to my server. I'll mail them this reply (parts of) and see what happens. /Martin S -- * *** This address is for technical email lists only*** *** Please use my primary mail address at the .org domain *** ***in all other matters *** * -- 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/20150721165159.horde.1dclwnrmwb4-oopcmkge...@www.skjoldebrand.eu
Re: Fetchmail may almost be working in pop3 Big Progress
To all who have helped me so far, a huge thank you! I soon realized that the subject line of this message is incorrect since pop3 covers only the delivery task and I got that working a couple of weeks or so ago. The indescribably joyful experience of being able to successfully authenticate to an out-going smtp smarthost that my ISP provides, however, has more than made up for the false sense of "mission accomplished" I felt when the first pop3 message popped up. I did take the output of an unsuccessful authentication attempt and ran the base64 string it returned as the password through base64 in decode mode and, voila, there was my user ID and password in nice clear text as it should be and there's where I found the last unexplainable reason for failure. In .msmtprc, there is a line that looks like: password 'BiG-SeCreT' I wanted to be really concise so I enclosed the secret in single quotes just as you see it here. I expected msmtp to strip those out and that would insure that what was there was always taken literally. What's there is taken literally, all right including the single quotes. I took them out and I can now see that authentication is successful and a couple of test messages went out and have arrived at a remote host in 1 piece so I technically can send mail but I still need to tie msmtp in to nmh which some of you may be familiar with. That is a different topic for a different mailing list. Again, thanks to all for your patience. Martin McCormick -- 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/20150721163034.ef1c822...@server1.shellworld.net
Re: File check at boot
Quoting Erick Ocrospoma : On 21 July 2015 at 10:32, Martin Skjöldebrand wrote: Hi, Mail from desperate user here: OS: Debian 8.1 Jessie Scenario: Mail/web server with file corruption. I have I/O errors on a few blocks which results in regular (daily) server crashes (including kernel panic) at random times during the day, usually afternoon CET. I need to run fsck on the disks. I have grub2 installed on the server. Catch: For some reason there is only one partition - yes I know this is retarded. Catch2: This is on virtual hosting provider so I can access the server through ssh or vnc but not physically How can I run fsck at boot time while the disks are umounted. Adding single to the grub linux kernel line fails to actually run fsck as the disk is mounted when server goes into rescue mode. I've Googled and (among other suggestions) read about the systemd fsck service but am not sure this will help or really how to invoke the thing properly Adding init=/bin/systemd fsck.mode=force fsck.repair=yes didn't seem to do much. Well, common fsck at boot procedure I ever used was: touch /forcefsck Thanks for suggestion. I've tried this but the server is back up in a few seconds, so I am fairly certain it isn't running a fsck at boot time after issuing "reboot". And the only half helpful suggestion from the hosting was running in single mode from grub, but the disk is mounted at that time. Else to rollback a snapshot of the server which would mean hours of reconfiguration which I am hoping to avoid. /Martin S -- * *** This address is for technical email lists only*** *** Please use my primary mail address at the .org domain *** ***in all other matters *** * -- 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/20150721162857.horde.nqperaiejios5-mved-x...@www.skjoldebrand.eu
Re: File check at boot
On 21 July 2015 at 10:32, Martin Skjöldebrand wrote: > Hi, > > Mail from desperate user here: > > OS: Debian 8.1 Jessie > > Scenario: Mail/web server with file corruption. I have I/O errors on a few > blocks which results in regular (daily) server crashes (including kernel > panic) at random times during the day, usually afternoon CET. I need to run > fsck on the disks. I have grub2 installed on the server. > > Catch: For some reason there is only one partition - yes I know this is > retarded. > Catch2: This is on virtual hosting provider so I can access the server > through ssh or vnc but not physically > > How can I run fsck at boot time while the disks are umounted. Adding > single to the grub linux kernel line fails to actually run fsck as the disk > is mounted when server goes into rescue mode. > I've Googled and (among other suggestions) read about the systemd fsck > service but am not sure this will help or really how to invoke the thing > properly > Adding init=/bin/systemd fsck.mode=force fsck.repair=yes didn't seem to do > much. > Well, common fsck at boot procedure I ever used was: touch /forcefsck Then rebooting server and waiting for it to be up. Most of the time it took several minutes due to fsck, I would wonder if trying witch systemd-fsck has taken a couple of minutes too? How are you sure that fsck is not running (asumming systemd-fsck is not working) ? On the other hand, as somebody else has told you, you should report this issue to your hosting provider, this is more a hardware problem than a OS/software one. > > > Desperate for suggestions. > > /Martin S > -- > Martin Skjöldebrand @ Home. > *** Please use my primary mail address at the .org domain if possible *** > > > -- > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.orgwith a > subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: > https://lists.debian.org/20150721153251.horde.zp7vphz7hkvhiiezwrax...@www.skjoldebrand.eu > > -- ~ Happy install ! Erick. --- IRC : zerick Blog: http://zerick.me About : http://about.me/zerick Linux User ID : 549567
Re: File check at boot
On 21/07/15 16:32, Martin Skjöldebrand wrote: Scenario: Mail/web server with file corruption. I have I/O errors on a few blocks which results in regular (daily) server crashes (including kernel panic) at random times during the day, usually afternoon CET. I need to run fsck on the disks. I have grub2 installed on the server. If you have "I/O errors on a few blocks", it seems to me that the hardware your virtual hosting provider uses to host your server is either defective, dying, or misconfigured, and you should address *that* as a matter of urgency. The systemd-fsck service *should* run automatically, as far as I can tell from casual inspection of the relevant systemd unit files, but if you are actually getting *I/O errors*, fsck is not going to save you. -- 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/55ae6ccd.7050...@zen.co.uk
File check at boot
Hi, Mail from desperate user here: OS: Debian 8.1 Jessie Scenario: Mail/web server with file corruption. I have I/O errors on a few blocks which results in regular (daily) server crashes (including kernel panic) at random times during the day, usually afternoon CET. I need to run fsck on the disks. I have grub2 installed on the server. Catch: For some reason there is only one partition - yes I know this is retarded. Catch2: This is on virtual hosting provider so I can access the server through ssh or vnc but not physically How can I run fsck at boot time while the disks are umounted. Adding single to the grub linux kernel line fails to actually run fsck as the disk is mounted when server goes into rescue mode. I've Googled and (among other suggestions) read about the systemd fsck service but am not sure this will help or really how to invoke the thing properly Adding init=/bin/systemd fsck.mode=force fsck.repair=yes didn't seem to do much. Desperate for suggestions. /Martin S -- Martin Skjöldebrand @ Home. *** Please use my primary mail address at the .org domain if possible *** -- 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/20150721153251.horde.zp7vphz7hkvhiiezwrax...@www.skjoldebrand.eu
Re: Debug files are given unreadable names
Hello and thanks for your reply. If this is indeed the current accepted way of providing debug symbols, that's ok but: 1) Do I understand that gdb as packaged with Debian and derivatives is capable of automatically accessing these files when required? 2) For those who want to examine these symbols using tools like nm, what is the solution? 3) The bug report says: - If people complained that filenames in -dbg packages are not transparent enough, a script that would print mapping between binaries and their .debug counterparts could be easily written, to be included in devscripts. Does such a script exist as of now? If not, could it please be provided as you mention above? Thanks! -- Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा -- 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/CAH-HCWX7w8C9sAGWdAzOzh-Yx1mVJaqwVXeUjOoEkUT=jnp...@mail.gmail.com
Re: Bizarre issue: USB 3 disconnecting and dying
Le tridi 3 thermidor, an CCXXIII, Jape Person a écrit : > I should probably be more careful in the way I word things. I meant to say > that *I* won't let USB-connected storage devices (or optical disc devices) > anywhere near /etc/fstab on my systems. With the default options, it could prevent the boot from finishing if the drive is not present. But with the noauto option, in terms of stability it is completely equivalent to mounting with mount or pmount: it is only a shortcut, and possibly a privileges delegation with the user option. Of course, it is only useful with stable names. Regards, -- Nicolas George signature.asc Description: Digital signature
Re: Debug files are given unreadable names
Am 21.07.2015 um 13:19 schrieb Shriramana Sharma: > I do not have enough knowledge of Debian build system to identify the > correct package to file the bug against. Please tell me if the bug is > already filed too. (I tried to use the search interface but trying to > "include bugs with" "debug symbols have unreadable names" did not work > correctly.) That's not a bug, but the package using build-ids now. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642158 why build-ids are wanted. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bizarre issue: USB 3 disconnecting and dying
On 07/20/2015 08:53 PM, Joel Rees wrote: I don't seem to be able to string two sentences together these days. I mean, I think Jape suggests removing the entries entirely. That's one possibility. I should probably be more careful in the way I word things. I meant to say that *I* won't let USB-connected storage devices (or optical disc devices) anywhere near /etc/fstab on my systems. I use pmount to handle mounting them and unmounting them. That works great for my simple personal systems, but I don't encrypt the external volumes, and I disconnect them when they are not mounted. If I need to store sensitive data externally I put it in a password-protected archive and then store it externally. The more complex systems I used at work (retired now) don't use external physical drives and use arrangements made on SANs for data backups. I would also suggest being sure that the UUID is correct, since you swapped actual media: See https://wiki.debian.org/fstab if you are not familiar with UUIDs and the blkid command. Otherwise, I'm out of useful suggestions. And this is what I should have said in my earlier post. Sorry. I think Joel's clarification is spot on. If I were going to use fstab for handling mounting chores for external drives UUID is certainly the way I'd go. I agreed with an end user creating his own Debian system once that labels would work as well as the UUIDs he detested the look of. He didn't understand that two external drives with the same label weren't what I meant. I was amazed. He was angry. Of course, it's also possible to mess up using UUIDs if one reassigns UUIDs. Yeah, that was this end user's next step. I'm just as dumb as him -- just not about this particular sort of thing. ;-) Jape -- 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/55ae3418.10...@comcast.net
Debug files are given unreadable names
Hello. Please compare: https://packages.debian.org/sid/amd64/libc6-dbg/filelist with the following: https://packages.debian.org/sid/amd64/libqt4-dbg/filelist https://packages.debian.org/sid/amd64/qtbase5-dbg/filelist https://packages.debian.org/sid/amd64/kdelibs5-dbg/filelist https://packages.debian.org/sid/amd64/libkf5guiaddons5-dbg/filelist https://packages.debian.org/sid/amd64/libkf5coreaddons5-dbg/filelist The libc6 debug package clearly shows the actual file names of the SO-s from which the debug symbols where extracted so that for instance even though I find: /usr/lib/x86_64-linux-gnu $ nm libm.so nm: libm.so: no symbols I can go to the identically named directory under /usr/lib/debug and: /usr/lib/debug/lib/x86_64-linux-gnu $ nm -C libm-2.19.so | grep sincos 00027530 W sincos 00027530 t __sincos 00034d80 W sincosf 00034d80 t __sincosf 0003f950 W sincosl 0003f950 t __sincosl 000aafe0 r __sincosl_table 000ade20 r __sincostab Clearly the Qt/KDE libs' debug symbols files should also have similar meaningful names identical to the actual SO files from which these symbols have been stripped, but there is probably some bug in the Debian builder scripts which automatically pull the git from upstream repo and builds it, or something like that, causing names to be similar to git blob file names. I do not have enough knowledge of Debian build system to identify the correct package to file the bug against. Please tell me if the bug is already filed too. (I tried to use the search interface but trying to "include bugs with" "debug symbols have unreadable names" did not work correctly.) Thanks. BTW I'm not subscribed to this list so I request being CC-ed on this thread. -- Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा -- 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/cah-hcwwf9odt-rgl0fzb3dh47gvwzb7rafwitg_zv4k3qar...@mail.gmail.com
