December 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] SuSE-13.1 and older kernels - no go
by Mark Hounschell 09 Dec '13

09 Dec '13

I have a need to run a 3.4.x flavor kernel on a 13.1 box. No problem on 12.3 but on 13.1 the same kernel faults immediately. I haven't put a serial console on to see the oops message but is there any reason it "shouldn't" work? Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

[opensuse] "paris" card deck for kpat
by jdd 09 Dec '13

09 Dec '13

Hello, may be seems minor, but why are the card decks of "kpat" (kde4 patience card game), so few now, and specially why is the "paris", best deck ever no more available? I had to catch it from my old install! I see no potential problem: http://osdir.com/ml/kde-games-devel/2009-05/msg00089.html thanks jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Re: [opensuse-factory] Re: zypper dup 12.2 -> 13.1 fail
by Carlos E. R. 09 Dec '13

09 Dec '13

On 2013-12-09 13:36, C wrote: > Off list reply... since it's not really important to the Factory list. > >>> System 2 is very difficult to upgrade, and for all the work it takes >>> to sort out the endless issues, it's easier, cleaner and infinitely >>> faster to backup, format the root partition, and reinstall. On these >>> systems, I'm up and running again in 10 minutes, and spend maybe 30 >>> minutes re-adding the repos and reinstalling 3rd party apps. >> >> It takes me weeks to install fresh with absolutely everything configured >> and tested. Things which are configured by root, not user, and thus do >> not reside on the home partition. > > For a "home" single user system? Then isn't that more likely to be > the System 1 config in that high level example? The System 2 config > I'm thinking of that I've had endless pain and sorrow with upgrading > is down to the long list of non-default repos I enable on my home > desktop. The server systems upgrade smoothly because they are running > the basics, nothing too alien. No, it is an hybrid. It is a certainly a desktop machine, but I use services like in a server for learning stuff. For instance, email is not handled by kmail or thunderbird, but fetchmail, postfix, amavis, spamassassin, procmail, dovecot... the full lot. I have ftp server, http, mysql, ntp, nfs, smb, leafnode, etc. More that I forget about. Of course, it is such a long time because I don't seat straight to configure everything in one go, full time. I have to do other things in between. For me it is simpler and faster to upgrade. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

1 0

[opensuse] Crontab : daily cron job for rkhunter on oS 13.1
by ellanios82 09 Dec '13

09 Dec '13

Hello List - i have a line in crontab : 30 12 * * * exec /usr/bin/rkhunter --cronjob --update --rwo ..................... it seems that rkhunter is not being run by crontab . . . any idea how to activate ? ............ thanks -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 12

[opensuse] systemd - socket activation for a service?
by Per Jessen 09 Dec '13

09 Dec '13

I'm upgrading a box to 12.3, and need to run a tftp daemon. systemd/tftp appear to come with a setup ready for socket activation. I would prefer running a permanent daemon, but thought I should try out the socket activation. I've enabled "tftp.socket", but nothing happens when the first tftp request arrives. Anything else I need to do? -- Per Jessen, Zürich (-0.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] fails: zypper install -C "debuginfo(build-id)=afa98667969782208459e394f8c8f87ac7510710"
by Bernhard Voelker 09 Dec '13

09 Dec '13

When running GDB, it warns about missing debug info for system libraries: Missing separate debuginfo for /lib64/ld-linux-x86-64.so.2 Try: zypper install -C "debuginfo(build-id)=afa98667969782208459e394f8c8f87ac7510710" Missing separate debuginfo for /lib64/libc.so.6 Try: zypper install -C "debuginfo(build-id)=add838dff54f86a92af42b775679db6000a0b676" ... but the suggested commands fail: $ zypper install -C "debuginfo(build-id)=afa98667969782208459e394f8c8f87ac7510710" Retrieving repository 'openSUSE-13.1-Update' metadata ..........................[done] Building repository 'openSUSE-13.1-Update' cache .................................[done] Loading repository data... Reading installed packages... No provider of 'debuginfo(build-id) = afa98667969782208459e394f8c8f87ac7510710' found. Resolving package dependencies... Nothing to do. Anyone getting this to work? Thanks & have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] RAID failure - md1: bitmap initialization failed: -5 (how to recover?)
by David C. Rankin 09 Dec '13

09 Dec '13

Guys, I have an older openSuSE box (11.0 i586) that serves as a backoffice fax server (hylafax/avantfax) that no longer boots due to a mdraid failure. At first I thought it would be a simple hardware drive failure where I could simply fail the drive, remove it from the array, replace it, and then rebuild, but that is not the case. I have poked around a bit, and it looks like the disk hardware is fine, but for some reason the bitmap file and superblock for the array cannot be found. I have copied the boot message from the screen and it is shown below: (booting fallback image) md: raid0 personality registered for level 0 xor: measuring software checksum speed <snip> xor: using function: p5_max (2935.000 MB/sec) async_tx: api initialized (sync-only) <snip> md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 md: md1 stopped. md: bind (sdb5) md: bind (sda5) md: md1 array is not clean -- starting background reconstruction raid1: raid set md1 active with 2 out of 2 mirrors md1: bitmap file is out of date (148 < 149) -- forcing full recovery md1: bitmap file is out of date, doing full recovery md1: bitmap initialization failed: -5 md1: failed to create bitmap (-5) md: pers->run() failed ... mdadm: failed to RUN_ARRAY /dev/md1: Input/Output error mdadm: device /dev/md1 already active - cannot assemble it Waiting for device /dev/md1 to appear: ok /dev/md1: unknown volume type invalid root filesystem -- exiting to /bin/sh $ The output from the normal boot image is the same aside from trying resume=/dev/sdb5 which fails. What is the best approach to attempt to correct the mdraid problem, or ignoring the raid issue, how do I recover the partitions from the disks? Attempting a normal mount (ro) from the recovery console fails due to unknown filesystem type (filesystem_raid) (I didn't catch the exact message). But that makes since, all the partitions are of type 'fd' 'Linux raid autodetect'. cat /proc/mdstat shows both disks used in the md1 array, but it doesn't know what personality it is. Manually attempting to mount /dev/md1 mount complains about unknown filesystem and unable to find superblock information. That just sounds bad... I don't know, but assume that reboot that produced the error was caused by a power outage where power was on and off several times long enough to exhaust the UPS. But that has happened numerous times and there has never been an issue on reboot. The big question is how to approach data recovery? Favorite links or tools? I have a write-up or two squirreled away somewhere from years past about dd/dd_rescue for copying the partitions, but I haven't done this on a md array before. Any help, or suggestions will be much appreciated. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 17

Re: [opensuse] RAID failure - md1: bitmap initialization failed: -5 (how to recover?)
by John Andersen 09 Dec '13

09 Dec '13

On 12/8/2013 6:19 PM, David C. Rankin wrote: > On 12/08/2013 07:31 PM, John Andersen wrote: >> Maybe a step missing in there: >> http://www.dslreports.com/forum/r21036244- > > Err.. bad link or 'members only' forum > http://www.dslreports.com/forum/r21036244- For some odd reason, the trailing dash appears in the text, but not the hyperlink under the text. Copy and paste seems to work, but what ever part of the mail system turns urls into links messes up a trailing dash -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] 12.3:susefirewall2: nfs exposed on external interface
by jdebert 08 Dec '13

08 Dec '13

Just a preliminary note: found nfs & rpc exposed on the external interface. susefirewall2 appears to be configured not to do that. At least, nfs & rpc are not on the allowed services list for external interface. susefirewall2 allowed external connections to all the mapped nfs ports. Information leaked about internal network configuration, several internal hosts, among other things. Found this because I was investigating many dropped packets logged by sfw2 earlier this morning to udp port 56216, which resembles the pattern seen where sfw2 drops packets from extablished connections. also noted that sfw2 is logging & dropping lots of packets from established connections, which probably explains why transfers are so incredibly slow. Also explains the constant resends and perhaps the many duplicate packets seen w/ wireshark. for the time being, nfs, rpc & portmap services are shut down while I investigate. y'all might want to take a look @ what sfw2 is allowing w/o your knowledge if you use it. Considering dumping sfw2 and using my own firewall configs. -- jd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 13

[opensuse] /var/log/messages : gnome keyring socket oS 13.1
by ellanios82 08 Dec '13

08 Dec '13

Hello List, In /var/log/messages i see : " The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring-I2wEPa/control 2013-12-08T20:32:32.629008+02:00 AIG su: gkr-pam: couldn't unlock the login keyring. " ............ - How to fix please ? thanks -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0