Re: [opensuse] How to manage 100+ linux boxes?
Xn Nooby schreef: Is there a standard way to remotely manage 100+ SUSE boxes? The machines are NLPOS9, which is based on SLES9, which is in turn based on SUSE 9.1. I need a way to remotely administer them, with cheaper solutions being ideal. The problem is having to individually log in and tweak things on 100+ boxes. The administration tasks would be applying security updates, and working with files for custom applications. I believe I can do this with two shell scripts, a "control" script and a "job" script. The control script would copy (via scp) and remotely run (via SSH) the job script to a list of servers stored in an ASCII file. Is this the standard way of doing this? Any suggestions? well, i should install 1 ( or maybe 2 ) LTSP servers, and turn the 100 suse boxes into thinclients with LTSP. Then you only have to manage 1 ( or 2 ) servers. This is a real dream from point of view administration. Of course it depends on what kind of applications needs to run on the thinclients. Realy worth thinking about a happy LTSP/OpenSUSe user jef peeraer -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] greeter goes wild
jef peeraer schreef: my greeter ( opensuse 10.2 ) does very weird. Every keyboard action changes the resolution of the screen. Someone seem this before? In the xorg.log everything seems normal. The detected device is -> Shared PCI/AGP Mach64 in slot 0:5:0 detected solved it. for the record, a file from libx11 was missing, xkbsymlib something. reinstalled libx11 and everything works now. thanks jef peeraer -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] greeter goes wild
my greeter ( opensuse 10.2 ) does very weird. Every keyboard action changes the resolution of the screen. Someone seem this before? In the xorg.log everything seems normal. The detected device is -> Shared PCI/AGP Mach64 in slot 0:5:0 detected thanks jef peeraer -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Recommendation for sata card?
>- Oorspronkelijk bericht - >Van: Robert Smits [mailto:[EMAIL PROTECTED] >Verzonden: vrijdag, mei 25, 2007 04:21 AM >Aan: 'OpenSUSE' >Onderwerp: [opensuse] Recommendation for sata card? > >I need a sata pci card to allow my suse 10.1 system to see a 320 GB sata >drive. Any recommendations? i use 3ware (AMCC) cards all the time. Rock stable and full linux support. jef peeraer >-- >Bob Smits [EMAIL PROTECTED] > >Windows - noun. 1. Global virus. 2. 32 bit extension and a graphical shell for >a 16 bit patch to an 8 bit operating system originally coded for a 4 bit >microprocessor, written by a 2 bit company that can't stand 1 bit of >competition. - Harry Martin >-- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] So many dbus-daemon print-pid processes...
Marcus Meissner schreef: On Thu, May 24, 2007 at 09:47:53AM +0200, Verner Kjærsgaard wrote: Hi list, - on a SuSE10.2 dual 64bit machine with 10+ users, a standard "ps auxw | grep -i print-pid | wc" gives me 650 instances of lines (like) this: victor 30770 0.0 0.0 4792 632 ?Ss 13:36 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session ...eh, can this be true? What is it, should I do something to get rid of them/it? My systemload is very often over 8.0 which I think is high... I just disabled Beagle autostart just for the same reason. Don't know yet if that lowers my system load. It should only have the same number of occurences as the number of logged in users. Its probably not getting terminated correctly on log-out. Ciao, Marcus see bugs 266931 and 158098 jef peeraer ps. just do a killall /usr/bin/dbus-daemon when everybody is logged out -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] A very interesting Virtualization Theory article
John O'Gorman schreef: I have installed the Xen kernel successfully on openSUSE 10.2 But my attempts to use Yast to create VMs have not worked as I expected. With the help of a friend I have been able to get VMs working and after quite a lot of fiddling about get all the GNOME graphical desktop stuff into working order. e.g. the Yast sinks back to text mode when installing VMs. Before wasting anyone else's time on this, can we expect the 10.2 version of Yast to be up to the job of fully creating and intalling VMs? After the trouble I had with paravirtualised VMs I am shrinking from attempting the fully virtualised ones (I have an IBM x3500 to try it on). My impression is that the openSUSE 10.2 Xen is also not up to date with the Xen site. I expect that this is inevitable. My ambition is that when I have mastered the use of Xen, I will upgrade all my client sites to using it so that upgrades for version to version of Linux may be less traumatic (for me) than they are now. Is it better to use the source from the Xen site and install VMs by hand using the basic commands vmcreate and so on, or persist with Yast? Can anyone knowledgeable comment on these points? John, do you mean that in the future, we will be able to install a new distribution by just copying one image ? i must say that i've already read some parts about virtualisation, but i thought a 64 bit system was needed for this, and my experiences with 64 bit versions are not that satisfying... jef peeraer -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Linux server company info
Jack Malone schreef: Hey taharka I will give them a look see. Thanks for info. hey jack, i have good experiences with supermicro motherboards, and they specify a compatibilty matrix. They have complete servers, or home grown. But indeed, if you want to be sure, and spend more money, a good server company can be of great help, my linuxjournal is full of these guys jef peeraer Jack -Original Message- From: taharka [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 3:39 PM To: Jack Malone Cc: opensuse@opensuse.org Subject: Re: [opensuse] Linux server company info How do, On Fri, 2007-05-11 at 13:47 -0500, Jack Malone wrote: I'm in the market for a new server for work here. I'm looking for some company that builds server class machines that are pretty much certified to run suse linux either version (enterprise or opensuse). I do not have to the have the os installed on it but it would be ok if it came with the machine. I need a raid 10 setup in the machine. I just want some good sources to start looking at that are known linux vendors. I know I can build my own machine up but at this point I'm ready to get a machine that I know will run suse with no problems, just have to plug the os into the machine an start working. How about giving these guys a try? http://www.rcubedtech.com/ Thanks in advance. Jack Malone taharka Lexington, Kentucky U.S.A. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] 3ware 9650se-8lpml second try
Jack Malone schreef: Ok I have the 3ware 9650SE-8LPML raid card to go into a machine. At the moment I cannot get suse 10.2 to see the card so that I can use it to install to hard drives attached to it. I know that suse has drivers built into it for 3ware cards but this card does not seem to be support as of yet. I'm wondering if anyone else here on the list has this card and using it with suse 10.2. What did you do to get it to work? I have had ubuntu 7.04 the, latest version that just came out, that will install onto hard drives attached to this card with no problem. But I want to use suse on this server. I have tried to load the driver at boot time from the install menu by hitting F5 then saying yes and pointing it to the floppy drive to get the driver. It just does not see the driver on the floppy for some reason. I made the driver disk from the cd that came with the 3ware card. At this point I'm at a standstill. I need to get this machine up and running ASAP. This is the first time I have had trouble using a 3ware raid card with suse linux. Thanks for any help anyone can give me on this. Jack Malone i have to install 2 servers with the 3ware 9550sx controller later this week. if i encounter problems ( or if it succeeds ), i'll let you know. i know it's hard when you get stuck with hardware, especially linux-friendly, and no-one on the list seems to have the same problems jef peeraer ps when you hit F5 ( i thought is was F2 ? ), can you watch the other consoles, because they print a lot of info there ( alt-f2/alt-f3 ). maybe you find some useffull info there -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] busy server -> lots of dbus daemons
Timo Hoenig schreef: Hi Jef, On Thu, 2007-04-26 at 23:13 +0200, jef peeraer wrote: i have a server , opensuse 10.2 , with a user load around 30. When people are logged out, i see a lot of these processes : gdens10522 0.0 0.0 3776 544 ?Ss Apr25 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session shermans 13141 0.0 0.0 3776 544 ?Ss 07:51 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session 1551913448 0.0 0.0 3772 544 ?Ss 08:01 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session scuypers 13687 0.0 0.0 3772 544 ?Ss 08:13 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session dmarien 13948 0.0 0.0 3772 544 ?Ss 08:17 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session 1552514239 0.0 0.0 3776 544 ?Ss 08:28 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session hlaenen 14467 0.0 0.0 3776 544 ?Ss 08:29 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session kbosman 14827 0.0 0.0 3772 544 ?Ss 08:32 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session scuypers 14861 0.0 0.0 3772 544 ?Ss 08:32 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session gdens15481 0.0 0.0 3772 540 ?Ss 08:36 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session wduerloo 15940 0.0 0.0 3772 544 ?Ss 08:38 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session 1551316209 0.0 0.0 3772 544 ?Ss 08:40 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session 1554016395 0.0 0.0 3776 540 ?Ss 08:40 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session aaerts 17544 0.0 0.0 3776 544 ?Ss 08:50 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session cmeynen 18503 0.0 0.0 3776 544 ?Ss 09:03 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session pwuyts 18766 0.0 0.0 3772 544 ?Ss 09:06 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session fhelsen 20364 0.0 0.0 3772 540 ?Ss 09:30 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session 1554123398 0.0 0.0 3772 544 ?Ss 10:48 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session sclaes 24036 0.0 0.0 3776 544 ?Ss 10:54 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session I suppose it is harmless, but it is trashing the ps If the users are logged out, the D-Bus session bus daemons should not be running any longer. See bugs #158098 and #266931 on http://bugzilla.novell.com . ok, i'll check it out this evening, when everyone is gone, but it is indeed when everybody is logged out. For the above state (users are logged out, session buses are still running): Can you please provide the complete output of 'ps axu' and attach it to one of the mentioned bugs? ok, later this evening. ps. i am running ltsp on this server, if that can help. jef peeraer Thanks, Timo -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] busy server -> lots of dbus daemons
i have a server , opensuse 10.2 , with a user load around 30. When people are logged out, i see a lot of these processes : gdens10522 0.0 0.0 3776 544 ?Ss Apr25 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session shermans 13141 0.0 0.0 3776 544 ?Ss 07:51 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session 1551913448 0.0 0.0 3772 544 ?Ss 08:01 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session scuypers 13687 0.0 0.0 3772 544 ?Ss 08:13 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session dmarien 13948 0.0 0.0 3772 544 ?Ss 08:17 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session 1552514239 0.0 0.0 3776 544 ?Ss 08:28 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session hlaenen 14467 0.0 0.0 3776 544 ?Ss 08:29 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session kbosman 14827 0.0 0.0 3772 544 ?Ss 08:32 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session scuypers 14861 0.0 0.0 3772 544 ?Ss 08:32 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session gdens15481 0.0 0.0 3772 540 ?Ss 08:36 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session wduerloo 15940 0.0 0.0 3772 544 ?Ss 08:38 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session 1551316209 0.0 0.0 3772 544 ?Ss 08:40 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session 1554016395 0.0 0.0 3776 540 ?Ss 08:40 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session aaerts 17544 0.0 0.0 3776 544 ?Ss 08:50 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session cmeynen 18503 0.0 0.0 3776 544 ?Ss 09:03 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session pwuyts 18766 0.0 0.0 3772 544 ?Ss 09:06 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session fhelsen 20364 0.0 0.0 3772 540 ?Ss 09:30 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session 1554123398 0.0 0.0 3772 544 ?Ss 10:48 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session sclaes 24036 0.0 0.0 3776 544 ?Ss 10:54 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session I suppose it is harmless, but it is trashing the ps jef peeraer -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] sles <-> opensuse
what are the basic differences , appart from the support being offered ? (sles 10 /opensuse 10.2). thanks jef peeraer suse fan from the first hour -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] dbus-daemon and other stuff
i've set up a server to be used as a TS for arround 30 users. it works great, but i have some minor issues . ( it's an opensuse 10.2 ) * i'll had to disable beagle, because it ate all my ram. is it possible, to let it run at night only, or when a user is logged out ? * if i do a ps auxw, when all users are gone, i see a lot of these processes (arround 100 or more ) /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session my ps list is growing to large * how do i disable sound completely * i'll try to create a pipe for my syslog-ng, but i'll keep getting these permission errors, although the permissions seems correct this is the pipe prw-rw 1 root root0 2007-03-23 23:44 check_vigor_messages these are the messages Mar 23 23:44:38 jwt kernel: Kernel log daemon terminating. Mar 23 23:44:39 jwt syslog-ng[20729]: syslog-ng version 1.6.11 going down Mar 23 23:44:39 jwt syslog-ng[20895]: syslog-ng version 1.6.11 starting Mar 23 23:44:44 jwt kernel: klogd 1.4.1, log source = /proc/kmsg started. Mar 23 23:45:05 jwt syslog-ng[20895]: Changing permissions on special file /dev/xconsole Mar 23 23:45:05 jwt syslog-ng[20895]: Changing permissions on special file /dev/tty10 Mar 23 23:45:05 jwt syslog-ng[20895]: Cannot open file /var/run/check_vigor_messages for writing (Permission denied) for the rest, it's nice to see the server running with 30 persons working on it :-) jef peeraer -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] downgrade 64->32 bit
Bernhard Walle schreef:
* jef peeraer <[EMAIL PROTECTED]> [2007-03-19 09:56]:
can i downgrade an installation from 64 bit to 32 bit ? i have opensuse
10.2 64 bit installed, but i experience system lockups. in the past they
went away by switching to the 32 bit version. it's a dual opteron system
, with everything thourougly tested.
If you system hangs in the 64-bit version, this is a bug and should be
fixed. Please open a bugreport and provide as much information as
possbile. We need the hardware information ('hwinfo'), when it
happens, etc. Do the keyboard LEDs blink? Are you able to connect from
another machine in the network? Can you still ping from another
machine? Does Ctrl+Alt+F1 work? Does sysrq work?
I think it's not possbile to 'downgrade'. You need to reinstall and
copy over the data.
ok, that's what i did this morning. and you're right that i should file
a bug for this, but it is very difficult when you're upgradung at a
client's site and people are waiting to work.
for now everything is working, except that i had to switch off beagle.
this kills my server when 20 or more people are working on it. maybe i
should start another thread for this...
jef
Regards,
Bernhard
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] downgrade 64->32 bit
can i downgrade an installation from 64 bit to 32 bit ? i have opensuse 10.2 64 bit installed, but i experience system lockups. in the past they went away by switching to the 32 bit version. it's a dual opteron system , with everything thourougly tested. jef peeraer -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] ldap ( libnss) -> crashing samba and others
i found the problem, described in a mail above. it seems that a faulty ldap db ( although i could query the ldap tree ) causes smb, su, tftp to crash. I think they shouldn't crash , so it is a bug somewhere...(libnss) after installation of a new ldap db, problems went away. what do i do next ? do i post more info here ? jef peeraer -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] dual opteron & opensuse 10.1 ( 64 bit )
i've installed opensuse 10.1 ( 64 bit ) on a dual opteron server ( h8ssl motherboard ), 2 gig of ram, a 3ware raid controller and all went well. The system was quite stanle for a week or two. Then i started getting these 'general protection errors', especially when tftpd ran. Later on samba could not start anymore ( and nscd / su also produces general protection errors ). I replaced the server with exact the same hardware, to rule out any hardware problems, but the same errors pop up. I even tried a latest kernel ( 2.6.19-smp ), but to no avail. Most strange i find is that the error started only after a while ( +- 5 persons working on the server ). Is this a kernel problem, or is this a specific 64 bit problem ? jef peeraer ec 15 00:34:30 BeWo kernel: in.tftpd[3782] general protection rip:2b302087e8f3 rsp:7fff8a4ccd78 error:0 Dec 15 00:34:32 BeWo kernel: in.tftpd[3783] general protection rip:2b302087e8f3 rsp:7fff8a4ccd78 error:0 Dec 15 00:34:36 BeWo kernel: in.tftpd[3784] general protection rip:2b302087e8f3 rsp:7fff8a4ccd78 error:0 Dec 15 00:34:42 BeWo kernel: in.tftpd[3785] general protection rip:2b302087e8f3 rsp:7fff8a4ccd78 error:0 Dec 15 00:34:50 BeWo kernel: in.tftpd[3786] general protection rip:2b302087e8f3 rsp:7fff8a4ccd78 error:0 Dec 15 00:34:59 BeWo kernel: in.tftpd[3787] general protection rip:2b302087e8f3 rsp:7fff8a4ccd78 error:0 Dec 15 00:35:35 BeWo kernel: in.tftpd[3788] general protection rip:2b302087e8f3 rsp:7fff8a4ccd78 error:0 Dec 15 00:36:47 BeWo kernel: in.tftpd[3789] general protection rip:2b302087e8f3 rsp:7fff8a4ccd78 error:0 Dec 15 00:38:35 BeWo kernel: in.tftpd[3801] general protection rip:2b302087e8f3 rsp:7fff8a4ccd78 error:0 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
