generic blog of schmidi2

/usr/lib/lxc/templates/lxc-debian -p /var/lib/lxc/vm0/

Samba moslty makes problems to me after updates which are hard to solve.

Last night I upgraded our company filesserver from debian entch to lenny. After a short test with my linux client and on my windows terminalserver, it seemed to work correctly. Well, this was quiet different the next morning.

Problem
The next day after the upgrade from debian etch to lenny, some guys were able to use all shares of the fileservers, others were not (those were a little angry).

Find cause
To debug the problem, add following two lines to your /etc/samba/smb.conf

log level = 3
log file = /tmp/samba.log

Now watch the logfile while you access the the share. This is my log:

…
[2009/05/06 18:34:50, 3] smbd/process.c:process_smb(1549)
 Transaction 328 of length 128 (0 toread)
[2009/05/06 18:34:50, 3] smbd/process.c:switch_message(1361)
 switch message SMBtrans2 (pid 13791) conn 0x96ff070
[2009/05/06 18:34:50, 3] smbd/trans2.c:call_trans2qfilepathinfo(3939)
 call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004
[2009/05/06 18:34:50, 3] smbd/trans2.c:call_trans2qfilepathinfo(3993)
 call_trans2qfilepathinfo: SMB_VFS_STAT of shell32.dll failed (No such file or directory)
[2009/05/06 18:34:50, 3] smbd/error.c:reply_unix_error(154)
 unix_error_packet: error string = No such file or directory
[2009/05/06 18:34:50, 3] smbd/error.c:error_packet_set(61)
 error packet at smbd/trans2.c(3994) cmd=50 (SMBtrans2) NT_STATUS_OBJECT_NAME_NOT_FOUND
…

== To solve ==

Now, Mr. Google said following after I searched for NT_STATUS_OBJECT_NAME_NOT_FOUND:
http://lists-archives.org/samba/30781-error-when-upgrading-to-samba-3-0-25b-nt_status_object_path_not_found.html

Well, in the last message of the thread, following can be read:
> A reboot in the Windows PCs was the solution.

Quit strange cause just one of the angry users didn’t shut down the pc over night. So I rebooted first my linux machine. Then all windows users had to reboot and some of them also had to manually delete all saved networkdrives (like k:) and restart the logon-script. The problem was vanished.

Not to forget

If the samba server was upgraded, always REBOOT the windows machines and manually DELETE and RECREATE the specific networkdrives.

If you want to change the language in LimeSurvey but nothing happens, you have to set the following configuration parameter (in config.php):

$translationmode = 1;

This strange “workaround” is required when your php installation has some bug (don’t ask me).

Much time has cost me to find this solution.

Source:
http://www.limesurvey.org/index.php/de/Deutsches-Forum/20128-ReGerman-eingestellt-aber-alles-noch-in-Englisch.html
http://docs.limesurvey.org/tiki-index.php?page=Installationsanleitung

To allow login per SSH without entering the password, execute with the asked user following commands (one line) on the client-machine:
(replace <REMOTESERVER> with the ip/hostname of your remote server)

cat ~/.ssh/id_rsa.pub | ssh root@<REMOTESERVER> ‘mkdir ~/.ssh/ 2>/dev/null ; cat >> ~/.ssh/authorized_keys ; cat ~/.ssh/authorized_keys | uniq > ~/.ssh/authorized_keys.tmp ; mv ~/.ssh/authorized_keys.tmp ~/.ssh/authorized_keys’

If you get the error File “~/.ssh/id_rsa.pub” not found cancel with CTRL+C, execute command ssh-keygen and just hit enter to response questions. After that, call the first command again.

Error

# vmware-config.pl
The VMware VmPerl Scripting API was not installed.  Errors encountered during
compilation and installation of the module can be found here:
/tmp/vmware-config0

You will not be able to use the “vmware-cmd” program.

Errors can be found in the log file:
‘/tmp/vmware-config0/control-only/make.log’

Solution
# apt-get update
# apt-get install libssl-dev

Following packages are now new installed on the system:
libc6-dev libssl-dev linux-kernel-headers zlib1g-dev

# vmware-config.pl

After vmware is now properly configured, you can savely remove those packages again (but – let it be).

Source
http://www.linuxquestions.org/questions/linux-software-2/vmware-server-install-error-the-vmware-vmperl-scripting-api-was-not-installed.-476129/

If PhpMyAdmin throws a timeout exception when you would want to make a mysql-dump (in GIBB, dump is called “dömp”), it’s somewhat depressing. But there is a solution called MySqlDumper:

www.mysqldumper.de/en/

Unfortunately a typo3 extension doesn’t exists yet.

If you wanna to someting like this:

 

for I in $(zgrep -H “from=<test@google.com>” /var/logs/*.gz 2>/dev/null)
do
  LOG_FILE=”`echo $I | cut -d ‘:’ -f 1`”
  DATETIME=”`echo $I | cut -d ‘:’ -f 2-4 | cut -d ‘ ‘ -f 1-3`”
  MAILID=”`echo $I | cut -d ‘:’ -f 5 | cut -d ‘ ‘ -f 2`”
  RECIPIENT_ADDR=”`zgrep $MAILID $LOG_FILE | grep ‘to=’ | cut -d ‘<’ -f 2 | cut -d ‘>’ -f 1`”
  echo “$DATETIME $RECIPIENT_ADDR”
done

You will notice sooner or later that this doesn’t work this way: The for-loop doesn’t only treat line-breaks as a new element but also space-characters. Well, how can that be solved, fast and easy. This way:

 

zgrep -H “from=<test@google.com>” /var/logs/*.gz 2>/dev/null | while read I
do
  LOG_FILE=”`echo $I | cut -d ‘:’ -f 1`”
  DATETIME=”`echo $I | cut -d ‘:’ -f 2-4 | cut -d ‘ ‘ -f 1-3`”
  MAILID=”`echo $I | cut -d ‘:’ -f 5 | cut -d ‘ ‘ -f 2`”
  RECIPIENT_ADDR=”`zgrep $MAILID $LOG_FILE | grep ‘to=’ | cut -d ‘<’ -f 2 | cut -d ‘>’ -f 1`”
  echo “$DATETIME $RECIPIENT_ADDR”
done

Error

From: root@javatux.tup.local. (Cron Daemon)
To: root@javatux.tup.local.
Subject: Cron <root@javatux> /etc/webmin/sysstats/sysstats.pl
Content-Type: text/plain; charset=UTF-8
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
Date: Tue, 15 Jul 2008 15:07:02 +0200
Message-Id: <1216127222.585803.27235.nullmailer@javatux.tup.local.>

WARNING (eval)(disk.pl 140) : bad output for blocs : procbususb 0 0 0 – /proc/bus/usb
WARNING (eval)(disk.pl 195) : bad output for inodes : procbususb 0 0 0 – /proc/bus/usb

Solution

Open webmin, goto webminstats and open the module “Disk”. Then click on the link “configure module”. Scroll down until you see the list with all watched filesystems. Deactivate the list-entry “/proc/bus/usb” or simply delete it.