search for: aserver

...hang-up sshd usually logs a warning and goes back to waiting... For some reason every couple of days it decides to die. I grabbed the log except below at the last crash. /dev/urandom is in use by other things on the system without difficulties (to my knowledge anyways...). Nov 21 20:59:20 aserver sshd[4059]: Connection from x.x.x.170 port 2222 Nov 21 20:59:20 aserver sshd[4059]: fatal: Bad protocol version identification: quit Nov 21 20:59:56 aserver sshd[4047]: Closing connection to x.x.x.18 Nov 21 21:04:28 aserver sshd[4092]: Connection from x.x.x.170 port 2258 Nov 21 21:04:28 aserver ssh...

...sophos@192.168.4.53::test @ERROR: auth failed on module test rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(359) And in the syslog file at the server: Jan 5 05:27:14 aserver rsyncd[2289]: name lookup failed for 192.168.1.2: Name or service not known Jan 5 05:27:14 aserver rsyncd[2289]: auth failed on module test from unknown (192.168.1.2) Any ideas of what could be causing this? I have read the manual, (well bits of it)and think I have the rsyncd.conf correct and...

...on call to ftruncate() has to fail, since a FIFO cannot be truncated to the size of the original file. This results in a reported error at the command line, even though the data actually copies as commanded. Example: ------------------------------------------------------ #scp -B -q afile auser at aserver.com:/tmp/fifofile_input scp: /tmp/fifofile_input: truncate: Invalid argument ---------------------------------------------- This results in the contents of the file 'afile' being copied into the remote fifo, but the error is reported and the exit status is also set to 1. Suggested fix: On...

...a = "nexxxo01\00" } { key = "WBA_PASSWD/UID/9720\00" data = "nexxxo01\00" } etc... Users are being authenticated against a Windows 2003 DC via winbind, with smb.conf config being: [global] workgroup = XXXRES security = DOMAIN password server = aserver.adomain log level = 1 ldap ssl = no winbind uid = 1000-10000 winbind gid = 500-2000 winbind separator = + winbind use default domain = Yes winbind enum users = yes winbind enum groups = yes and nsswitch.conf entries: passwd:...

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

Hi everybody, Today I tried the latest Solaris on Xen build. I downlaoded all files and created the iso. Then I wanted to run setup_install_server , but this failed: bash-3.00# ./setup_install_server /export/sol_xen/ -bash: ./setup_install_server: cannot execute binary file -bash-3.00# So I create a tar file to copy over all files to export/sol_xen/ Then I tried to start and install via

1 simple question about network statistics for vnics: We noticed that the statistics for vnics (used by Virtualbox guests) are not there. When the nics are plumped in the host OS, we do see them showing up, but all all records are 0. Can someone tell me how to get the correct network info via snmp on the Vbox Host?? Thanks in advance. IF-MIB::ifDescr.1 = STRING: lo0 IF-MIB::ifDescr.2 = STRING:

Last 2 weeks we had 2 zpools corrupted. Pool was visible via zpool import, but could not be imported anymore. During import attempt we got I/O error, After a first powercut we lost our jumpstart/nfsroot zpool (another pool was still OK). Luckaly jumpstart data was backed up and easely restored, nfsroot Filesystems where not but those where just test machines. We thought the metadata corruption

We are currently experiencing a very huge perfomance drop on our zfs storage server. We have 2 pools, pool 1 stor is a raidz out of 7 iscsi nodes, home is a local mirror pool. Recently we had some issues with one of the storagenodes, because of that the pool was degraded. Since we did not succeed in bringing this storagenode back online (on zfs level) we upgraded our nashead from opensolaris b57