April 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Grub of a new install incomplete
by Constant Brouerius van Nidek 24 Apr '14

24 Apr '14

On my fresh installed 13.1 from a DVD I discovered that the menu.lst does not show a proper Failsafe possibility. The text for the normal boot is exactly the same as for Failsafe. the same situation for the two other available kernels. Do not know what caused the problem but would like to find out how to repair it. Editing the menu list by hand is a possibility but would that keep up with future kernel updates? Somebody else with this abnormality? A bug? -- Linux User 183145 using KDE4 and LXDE on a Pentium IV , powered by openSUSE 13.1 (i586) Kernel: 3.14.1-24.geafcebd-default KDE Development Platform: 4.12.4 21:18pm up 19:48, 3 users, load average: 1.07, 0.76, 0.71 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] nfs fails to start
by Patrick Shanahan 24 Apr '14

24 Apr '14

Tumbleweed kernel-desktop-3.14.1-24.2.geafcebd.x86_64 Had to reboot last night and cannot start nfs :^( systemctl status nfs nfs.service - LSB: NFS client services Loaded: loaded (/etc/init.d/nfs) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: failed (Result: timeout) since Tue 2014-04-22 10:40:42 EDT; 8min ago Process: 15602 ExecStart=/etc/init.d/nfs start (code=killed, signal=TERM) Apr 22 10:39:14 Crash nfs[15602]: mount.nfs: mount options: "rw,bg,retry=5,_netdev" Apr 22 10:40:42 Crash systemd[1]: nfs.service operation timed out. Terminating. Apr 22 10:40:42 Crash systemd[1]: Failed to start LSB: NFS client services. Apr 22 10:40:42 Crash systemd[1]: Unit nfs.service entered failed state. Apr 22 10:43:28 Crash mount[16304]: mount to NFS server '192.168.1.3' failed: timed out, retrying Apr 22 10:43:28 Crash mount[16303]: mount to NFS server '192.168.1.3' failed: timed out, retrying Apr 22 10:43:28 Crash mount[16305]: mount to NFS server '192.168.1.3' failed: timed out, retrying Apr 22 10:47:43 Crash mount[17037]: mount to NFS server '192.168.1.3' failed: timed out, retrying Apr 22 10:47:43 Crash mount[17038]: mount to NFS server '192.168.1.3' failed: timed out, retrying Apr 22 10:47:43 Crash mount[17041]: mount to NFS server '192.168.1.3' failed: timed out, retrying stopped nfs restarted rpcbind restarted nfs still failed rpcbind is active/running suggestions? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 28

[opensuse] Force nfs umount (hard, no intr)
by Robin Roth 24 Apr '14

24 Apr '14

Hi! a NFS server died and I have a nfs-client which still has a mount using nfs3 with option hard and no option intr. I failed to unmount, even "umount -fl /mountpoint " just hangs. With this hanging mount I can't use df, quota, ... I'm aware it was not the best idea to use hard without intr, but with this said and not being able to restart the server, is there a way to force the umount? I already tried to setup a fake interface with the original ip and also setup a nfs server at the original ip with the same share. Both attempts did not help. Thanks, Robin

1 1

[opensuse] virtual server: managing sevral servers with only one IP
by jdd 24 Apr '14

24 Apr '14

Hello, till now I had only one virtual machine on my server, so no real problem. but now I would like to host an other virtual machine. both virtual servers should have http, postfix/dovecot/inn and of course ssh capability at least. of course I have only one IP (V4, may be several IPV6 if usefull) for ssh I use simply an other port and SuSEfirewall2 forwards it ok, I can connect to manage the server(s). for http, I try to forward the port 80 from an other port, but this dont seems to work (but may be due to other problem like host name) - I should be able to solve this with apache or nginx.. but what is the prefered way for mail and news? is it enough to ask users to give a non standard port? (and does this works?) 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 1

[opensuse] Apropos tomboy (A simple note-taking application for Gnome)
by Carlos E. R. 23 Apr '14

23 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This is an application I find very useful. I use it in xfce, not gnome. I have now tons of notes. Instead of writing plain text files and keep it in a directory, I write a note in tomboy. You can have links from one to other, or to external files or webpages, and have some simple formatting (too simple some times). I only have a nagging problem with it: how can I sync notes between two or more computers? Somebody has done it? - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlNUGagACgkQtTMYHG2NR9UTNgCfe1t+pUrmB27eGypsth+Pyh6Y fmAAn2LstJAb2Pn/JWxLlnk3LLqSN4O/ =+UGS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

Re: [opensuse] System not starting!
by Benjamin Draxlbauer 23 Apr '14

23 Apr '14

Hi! System Opensuse 13.1 Kernel 3.11 Kde Desktop graphics nvidia optimus running with bumblebee. Actually i do not think, that it is a graphic issue, insofar as nothing has changed in the last few days and the splash screen with the opensuse chameleon and the flower is showing up, so the system is loading some stuff but hangs up somewhere ...but i might be worng on this ... I meant, that the system is hanging just before the second start screen comes, where there is the box with the filesystem, network kde etc. Actually i do think that i might have changed some stuff in /etc/sysctl editor in yast or with regard to the runlevels init.d , but not being aware of it. Console...That is what is most problematic - I can not even log in into the rescue console or any other console (CTRL-ALT-F1/F2), i can just watch the system starting up and hanging exactly after server 389 is reached... The script was just a small bash script with two lines like this exec=/usr/bin/unison -batch Thanks for help! Benjamin. Gesendet: Mittwoch, 23. April 2014 um 08:26 Uhr Von: "Carl Hartung" <opensuse(a)cehartung.com> An: opensuse(a)opensuse.org Betreff: Re: [opensuse] System not starting! Hi Benjamin, Questions interspersed... On Wed, 23 Apr 2014 09:40:05 +0200 Benjamin Draxlbauer wrote: > Hi everyone! > I have a serious problem...Since yesterday my system hangs up Please describe 'system' ~ architecture, desktop environment, versions and any special graphics card (nVidia, etc.) or other relevant hardware (e.g. RAID) > will start up and does not enter... Actually booting works and i can > also see the start screen, but not the screen when the modules and > kde is loaded. This is even the same problem with the recovery mode. I'm interpreting this to mean the usual graphical log-in greeter does not appear. Is this correct? Please confirm you're able to log into a console. > I took a look inside zypper log if something has been changed - via a > life usb system- but nothing which should concern the system. I also > took a look at /var/log/messages but also there seems to be no entry > with regard to the problem. > What might be the problem is that i was trying to get a small script > working which should sync some folders... If it's really a. small script (only several lines long,) share it here (obfuscate any sensitive details) and please explain, briefly but precisely, what you intend the script to do. > i placed this in /etc/init.d and made it executeable and made > symbolic links to this script in rc0.d and rc6.d. That is all. I > already deleted the files, but still the same problem... > > my system hangs up at the point directly after the server directory > 389 is reached and is marked with the green OK in the startup > screen...Unfortunately I also do not know more... Thanks for help - > Benjamin! Thanks & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 18

Re: [opensuse] System not starting!
by Carlos E. R. 23 Apr '14

23 Apr '14

On 2014-04-23 15:05, Benjamin Draxlbauer wrote: >> Are you intentionally running that service? Because if you are, I >> know nothing about it. > > No i am not running it intentionally, I already googeled the 389 > directory but i could not make sense of it. I thought of removing > LDAP but i do not know how insofar as i cannot even start the > konsole. Is it possible to change packages and stuff like this in the > recovery mode of with a live usb stick? I already tried this but > after loggin in as root, i could not find the zypper command... Well, that package doesn't install automatically. You must have added an extra repository yourself, because it is not part of the standard distribution, and then selected that thing to install... At this point, I can not imagine what else have you installed or done to your system... I would consider reinstall system from scratch as the most sensible route. Here: http://directory.fedoraproject.org/wiki/Howto:systemd they describe what files are added to activate it on a fedora system. If openSUSE does the same, I would try to remove those service and target files: /lib/systemd/system/dirsrv@.service /lib/systemd/system/dirsrv.target /etc/systemd/system/dirsrv.target.wants/ /etc/sysconfig/dirsrv.systemd Maybe that would allow the system to boot, or maybe not - I have no idea if something else is expecting that system to be running! This is like having a modern computerized car not starting, and try to solve it by removing pieces with a hacksaw. I have no idea what you have done to your system or why. Maybe when all that is left of the car are the wheels and frame it will run - by pushing it by hand. :-( -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

4 4

[opensuse] 13.1 32 bits refuses to mount DVD.
by Carlos E. R. 23 Apr '14

23 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have got this situation: AmonLanc:~ # mount -v /dev/sr0 /mnt/dvd/ mount: no medium found on /dev/sr0 AmonLanc:~ # However: AmonLanc:~ # hwinfo --cdrom 19: SCSI 100.0: 10602 CD-ROM (DVD) [Created at block.249] Unique ID: KD9E.cEI0dcpbs4E Parent ID: 3p2J.fcD2_aXgw74 SysFS ID: /class/block/sr0 SysFS BusID: 1:0:0:0 SysFS Device Link: /devices/pci0000:00/0000:00:1f.1/ata2/host1/target1:0:0/1:0:0:0 Hardware Class: cdrom Model: "SONY CD-RW CRX830E" Vendor: "SONY" Device: "CD-RW CRX830E" Revision: "JYK1" Driver: "ata_piix", "sr" Driver Modules: "ata_piix" Device File: /dev/sr0 (/dev/sg1) Device Files: /dev/sr0, /dev/cdrom, /dev/cdrw, /dev/disk/by-id/ata-SONY_CD-RW_DVD-ROM_CRX830E, /dev/disk/by-label/openSUSE-13.1-DVD-i5860091, /dev/disk/by-path/pci-0000:00:1f.1-scsi-1:0:0:0, /dev/disk/by-uuid/2013-11-06-20-12-49-00, /dev/dvd Device Number: block 11:0 (char 21:1) Features: CD-R, CD-RW, DVD, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL, DVD+RW DL, BD, BD-R, BD-RE, HD, HD-R, HD-RW, MRW, MRW-W Drive status: no medium Config Status: cfg=yes, avail=yes, need=no, active=unknown Attached to: #9 (IDE interface) Drive Speed: 47 AmonLanc:~ # As you can see, the DVD is seen, the correct by-label link has been created: AmonLanc:~ # l /dev/disk/by-label/openSUSE-13.1-DVD-i5860091 lrwxrwxrwx 1 root root 9 Apr 20 22:37 /dev/disk/by-label/openSUSE-13.1-DVD-i5860091 -> ../../sr0 AmonLanc:~ # file -s /dev/disk/by-label/openSUSE-13.1-DVD-i5860091 /dev/disk/by-label/openSUSE-13.1-DVD-i5860091: symbolic link to `../../sr0' AmonLanc:~ # file -s /dev/sr0 /dev/sr0: writable, no read permission AmonLanc:~ # AmonLanc:~ # eject /dev/sr0 eject: unable to eject AmonLanc:~ # AmonLanc:~ # eject -v /dev/sr0 eject: device name is `/dev/sr0' eject: /dev/sr0: not mounted eject: /dev/sr0: is whole-disk device eject: /dev/sr0: is removable device eject: /dev/sr0: trying to eject using CD-ROM eject command eject: CD-ROM eject command failed eject: /dev/sr0: trying to eject using SCSI commands eject: SCSI eject failed eject: /dev/sr0: trying to eject using floppy eject command eject: floppy eject command failed eject: /dev/sr0: trying to eject using tape offline command eject: tape offline command failed eject: unable to eject AmonLanc:~ # If the system created the label, it did read the disk at sometime. The problem is the "Drive status: no medium" thing, which is false, obviously. This was working sometime back. Obviously, as I installed openSUSE using that same DVD. syslog says nothing about it, nor dmesg. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlNVtGcACgkQtTMYHG2NR9XRXQCcC1McTg4drB2ajqzZJpdJxXI1 AOwAn0tqV+v7V33jEZRyiJf2IH20093L =bbTd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 14

[opensuse] virtual server problem: name resolve
by jdd 23 Apr '14

23 Apr '14

Hello, I host for now some years a personal server as virtualbox guest. Host is also mine. host is 12.3 I have a guest with 12.3 that works without problem. I now have to add an other virtual machine and installed 13.1. Really it was a 12.1 server upgraded to 13.1. this last one almost works. It's set up as much as I can see exactly like the working one (route ok, same dns in yast...) I can even connect to it from my home through ssh (using port 31022 forwarded to 22). from it (call it "s-r"), I can ping the exterior with IP, so I can ping the provider dns server, but the name do not resolve example, from s-r: s-r:~# ping ovh.fr ping: unknown host ovh.fr s-r:~ # ping 213.186.33.33 PING 213.186.33.33 (213.186.33.33) 56(84) bytes of data. 64 bytes from 213.186.33.33: icmp_seq=1 ttl=59 time=4.37 ms what can I do to fix this? I can provide any info you want 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 3

[opensuse] ssh to drop tcpwrappers support
by Lew Wolfgang 23 Apr '14

23 Apr '14

Found on the openssh-unix-dev list: Subject: heads up: tcpwrappers support going away Date: Tue, 22 Apr 2014 17:33:59 +1000 (EST) From: Damien Miller <djm(a)mindrot.org> To: openssh-unix-dev(a)mindrot.org Hi, This is an early warning: OpenSSH will drop tcpwrappers in the next release. sshd_config has supported the Match keyword for a long time and it is possible to express more useful conditions (e.g. matching by user and address) than tcpwrappers allowed. Removing it reduces the amount of code in the 'hot' pre-authentication path in sshd and rids us of a dependency. -d I've been using tcpwrappers with ssh for a long time. I was able to get sshguard working on openSuSE 12.2, but it wasn't easy. I'll have to give it a spin with 13.1 to see if things have improved. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4