Re: [sisuite-users] Permission bits on / are drwxr-x--x rather than drwxr-xr-x on autoinstalled client

2007-09-28 Thread Andrea Righi
wtautz wrote:
 Hi, I have noticed that on some autoinstalled clients that
 the root / directory has permissions:
 
 
 drwxr-x--x
 
 where as the golden client has drwxr-xr-x
 
 the golden client is Ubuntu Feisty, amd64 and I used systemimager
 version 3.8.2-2
 and the same version on the server.
 
 Is this a known behaviour?
 
 walter
 

It doesn't seem to happen with 3.9.6, anyway AFAIR nothing have been changed in
this front, so it's should be the same also with 3.8.2.

What are the permissions of your image in /var/lib/systemimager/images on your
image server?

-Andrea

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


[sisuite-users] No Logging

2007-09-28 Thread David . Livingstone
I am currently PXE booting  HP Proliant  servers with systemimager 3.9.6 
and while
the imaging is successful I have no logging on the server.

The systemimager server is a  HP Proliant DL380G4 running  the latest RH 
ES 4.
 
On the server I use si_mkdhcpserver I specified the log server and the 
port as
shown in the dhcpd.conf file below :

# log-servers
option log-servers 192.168.81.35;

# option-141 is the port number your log server uses
option option-141 8181;

On the server the the systemimager-server-monitord service is running - 
here
is the ps trace :
/usr/bin/perl -w /usr/sbin/si_monitor --log 
/var/log/systemimager/si_monitor.log --log_level 2

After a successful PXE boot/loading there is nothing in this file and by 
using netstat on the
server I cannot see and connection to port 8181.

From another machine I have connected to this port and I do get debug 
information
in the log ie

Fri Sep 28 09:11:19 2007: warning: bad request from 192.168.81.26 (mac
address not specified)!

Any help would be appreciated.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [sisuite-users] No Logging

2007-09-28 Thread Bryan Washer
You need to edit the APPEND line in your boot file on the PXE
serverhere is an example of one of mine...

 

APPEND vga=extended  initrd=i386_standard_initrd root=/dev/ram
MONITOR_SERVER=192.168.118.244 MONITOR_CONSOLE=yes

 

Notice the MONITOR_SERVER= and MONITOR_CONSOLE=yes

 

MONITOR_SERVER=a.b.c.d is needed to active the monitoring of the
installation

 

And

 

MONITOR_CONSOLE=yes is needed if you would like to be able to see a
mirror of the console while the system in imaging.

 

Hope this helps.

 

Bryan Washer

Sr. Systems Administrator

Vitesse Semiconductor Corp

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, September 28, 2007 10:30 AM
To: [EMAIL PROTECTED]; sisuite-users@lists.sourceforge.net
Subject: [sisuite-users] No Logging

 


I am currently PXE booting  HP Proliant  servers with systemimager 3.9.6
and while 
the imaging is successful I have no logging on the server. 

The systemimager server is a  HP Proliant DL380G4 running  the latest RH
ES 4. 
  
On the server I use si_mkdhcpserver I specified the log server and the
port as 
shown in the dhcpd.conf file below : 

# log-servers
option log-servers 192.168.81.35;

# option-141 is the port number your log server uses
option option-141 8181; 

On the server the the systemimager-server-monitord service is running -
here 
is the ps trace : 
/usr/bin/perl -w /usr/sbin/si_monitor --log
/var/log/systemimager/si_monitor.log --log_level 2 

After a successful PXE boot/loading there is nothing in this file and by
using netstat on the 
server I cannot see and connection to port 8181. 

From another machine I have connected to this port and I do get debug
information 
in the log ie

Fri Sep 28 09:11:19 2007: warning: bad request from 192.168.81.26 (mac
address not specified)! 

Any help would be appreciated. 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [sisuite-users] No Logging

2007-09-28 Thread David . Livingstone
Bryan,

 Thanks for the information ... now I see that man si_monitor does give 
:

Clients must have defined the MONITOR_SERVER (and optional MONITOR_PORT)
as boot parameters to enable the monitoring feature.

Is this documented anywhere else ?

Thanks


David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3050
Email: [EMAIL PROTECTED] 



Bryan Washer [EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
2007/09/28 11:08
Please respond to
sisuite-users@lists.sourceforge.net


To
sisuite-users@lists.sourceforge.net, [EMAIL PROTECTED]
cc

Subject
Re: [sisuite-users] No  Logging








You need to edit the APPEND line in your boot file on the PXE server?.here 
is an example of one of mine?

 

APPEND vga=extended  initrd=i386_standard_initrd root=/dev/ram 
MONITOR_SERVER=192.168.118.244 MONITOR_CONSOLE=yes

 

Notice the MONITOR_SERVER= and MONITOR_CONSOLE=yes

 

MONITOR_SERVER=a.b.c.d is needed to active the monitoring of the 
installation

 

And

 

MONITOR_CONSOLE=yes is needed if you would like to be able to see a mirror 
of the console while the system in imaging.

 

Hope this helps.

 

Bryan Washer

Sr. Systems Administrator

Vitesse Semiconductor Corp

 




From:[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of 
[EMAIL PROTECTED]
Sent: Friday, September 28, 2007 10:30 AM
To: [EMAIL PROTECTED]; sisuite-users@lists.sourceforge.net
Subject: [sisuite-users] No Logging

 


I am currently PXE booting  HP Proliant  servers with systemimager 3.9.6 
and while 
the imaging is successful I have no logging on the server. 

The systemimager server is a  HP Proliant DL380G4 running  the latest RH 
ES 4. 
  
On the server I use si_mkdhcpserver I specified the log server and the 
port as
shown in the dhcpd.conf file below : 

# log-servers
option log-servers 192.168.81.35;

# option-141 is the port number your log server uses
option option-141 8181; 

On the server the the systemimager-server-monitord service is running - 
here 
is the ps trace : 
/usr/bin/perl -w /usr/sbin/si_monitor --log 
/var/log/systemimager/si_monitor.log --log_level 2 

After a successful PXE boot/loading there is nothing in this file and by 
using netstat on the 
server I cannot see and connection to port 8181. 

From another machine I have connected to this port and I do get debug 
information 
in the log ie

Fri Sep 28 09:11:19 2007: warning: bad request from 192.168.81.26 (mac
address not specified)! 

Any help would be appreciated. 
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users