Teamspeak on Lniux

I decided to run Teamspeak on Linux today.

After downloading the tar, I decompressed it /etc/ by following the documentation.

The next task was to copy the data from my old system. As the drive is already mounted in the file system, the process was a breeze. The files to copy are

  • server.dbs
  • server.ini
  • server.log
  • I copied these files into the TS folder and double-checked the permissions. With owner permissions set sa ‘John’, I navigated to the directory /etc/tss2_rc2. Next step was the startup command ./teamspeak2-server_startscript start

    Just make sure that you’re not running the server as root (otherwise it will kick up an error), and everything seems to work ok.

    The only thing I now need is how to get the thing to run when I turn on the PC.

    Windows Files Systems and Booting Woes

    The battle is on. Me vs. the Windows disk structure.

    It’s been brewing for some time now. It was only two weeks ago that I had to rebuild a server as the hard disk had began to fail. Quite phenomenally I might add. It was a race against time to copy all of the critical data away from the beast for all of the user accounts.

    Of course, this in itself was quite a battle as backing up the system didn’t seem to be on some people’s primary agenda. Therefore the system that I recovered was about 1 month old. Not very good.

    Oh, and restoring an AD that old creates a new problem as Windows expects the restore to be fairly recent. If you’re having trouble after a restore and the event log gives some cryptic message about Volume Shaddow Copy dates and updates, you need to roll-back the system clock so that it doesn’t think that you’re doing anything dodgy.

    Then an arduous task of copying all of the data back into the relevant partitions ensued.

    Anyway, that’s not exactly the latest news. The recent events occurring are that I now have another failed drive on my hands at a second site. This time, there are bad sectors appearing on the disk.

    The story began with one of the staff performing a defrag on the server as part of a daily task. He also noticed that there were a startling number of errors in the event log that seemed to have to appear out of nowhere over a recent few days.

    The defrag caused the blue screen of death and the server would no longer start. chkdsk /r was ran in recovery console and reported various errors.

    ARGH! It gets worse. Bad sectors were bleeding across the disks like cancer. Time to act people!

    Thankfully, there’s a damn nifty Linux tool for copying drives. dd_rescue. It doesn’t have a startling homepage, but it does come with most Linux distros, including Knoppix.

    dd_rescue cloned the disk to another disk, ignoring all bad sectors. Once the system was copied we faced the next challenge. The Windows boot sector was firked. Bootcfg, Fixboot and Fixmbr wouldn’t work. Or more accurately, they did work – just not very well. In fact, booting into a Windows PE session showed that two of the drive’s partitions had switched letters. The system disk was now D!

    Various trickery ensued, but the final resolution was to install Windows Server the existing disk (that was thought to be D:), under a folder called Win2k3. Unfortunately, Windows was still under the impression that the system disk is D:. I followed the instructions for reconfiguring the hard disk drives through the registry on the Microsoft site.

    One final reboot later, allowed me to boot into the existing O/S and repair it with the setup disk. It’s such a shame that in the process – loads of MS SQL and Windows components were shot.

    WSUS is completely messed up and the SQL engine has also knocked out McAfee’s network deployment tool. I think that it’s a poorly server now.

    I just wish that clients would listen when I tell them that a backup device of any sort is crucial (as well as actually doing it). Alas, the attitude nowadays seems to be a mired philosophy of locking the door once the horse has bolted – and hoping that you never need to.

    Nokias Don’t Like Baths

    My Nokia went for a swim in my bathroom on Saturday.

    If only for a few seconds – it caused the phone great distress throughout the day. Even after removing the XPress on covers and drying it down with a tea-towel, it wasn’t happy.

    As the day progressed, the screen displayed a wonderful array of psychedelic colours and images. But the phone really only started working properly in the evening. Clearly it all dried out.

    The moral of this story is – don’t use your phone while shaving.

    I’m Tired and My Palm Don’t Love Me

    I almost fainted yesterday.

    I took my T3 Palm out of my pocket and pressed address book. The screen was blank.

    I gulped.

    I slid open the screen which is set to fire up the Palm. Nothing.

    I stopped breathing.

    Finally, I pressed the power button.

    Nothing. Nada. A sausage not.

    My Palm’s battery had decided that it had had enough for the day.

    The reason that this is so bothersome is that as most Palm users will tell you – a flat battery is the equivalent to carrying out a hard reset. All data on the Palm is lost. The real annoyance is that I haven’t been able to back up my Palm because I’ve been using Linux. The experience is becoming a painful one to say the least. Simple things like Synchronising my Palm is awkward and difficult because the closest I have got to a synchronisation is the following error message in KPilot:

    Pilot device /dev/ttyUSB1 is not read-write.

    Of course – being a DOS/Windows native, the obvious answer hadn’t occurred to me, which I found on the SuSE Linux Forums

    It turns out that the error message is telling me exactly what I need to know. The USB device doesn’t have read/write permissions. Well, not when I’m a standard user anyway.

    So running chmod 04666 /dev/ttyUSB1 (USB1 is the port I happen to be using) as root admin will make the USB port read/writeable for all users. Hooray!

    The only drawback is that now I finally have the thing synchronising – I need to go back to Windows to be able to (hopefully) restore my settings Before Linuxing it. I’ll see how that goes…

    Logitech USB Headset and Linux

    I’ve been having a battle with my Logitech USB headset over the last couple of days. If there’s on thing I liked in Windows a great deal, that was the simplicity of the USB headset.

    If I plug it in, all the sound would be defaulted to the headset. When unplugged, the sound would go back to the sound card. It was beautiful.

    Linux, on the other hand, wouldn’t play like that. SUSE’s YaST doesn’t like the USB headset. It knows that something is there. It even knows that there is some sort of sound device there. But it doesn’t recognise it. Neither does it want to know.

    I was having all sorts of grief the thing. In fact I couldn’t tell whether it was working or not half the time.

    I hit the Novell SUSE Hardware forums and posted a request, and received the following advice:

    As far as I understood the wrong driver gets selected during boot.

    add “audio” to “/etc/hotplug/blacklist”, plug in the headset and then
    reboot. /proc/asound/cards should show something like “USB-Audio – C-Media
    USB Headphone Set”

    alternatively edit /etc/modprobe.conf (or modprobe.conf.local):
    alias snd-card-0 snd-intel8x0
    alias snd-card-1 snd-usb-audio
    options snd-intel8x0 index=0
    options snd-usb-audio index=1

    After rebooting the USB Headset didn’t seem to appear in YaST again. However, KMIX and QAMix both recognised the new hardware device.

    After switching off ‘mute’ for the headset mic (which is enabled by default), everything seems to work.

    The only catch is that I have to have the headset plugged in when I start Linux, and I can’t reconnect it during a session. B’ah!

    The good part is that Skype works a treat now.

    Win2Lin Day 2

    So here I am on the Linux PC.

    I’m growing increasingly frustrated at the various flavours of Linux, and the subtle differences between them. So much so that I can’t even find a simple command line to restart the samba server.

    the IMAP server seems to be fickle. I can’t get Squirrelmail to show me the inbox. It could possibly be due to the vast number of emails that I have copied in. Yet, I thought that’s the whole point of IMAP – to work speedily across a network? Hmm.

    fetchmail and fetchmailconf caught me out a couple of times today. The final moment was when the fetchmail daemon wasn’t downloading my emails. I realised that I had configured fetchmail as my user, rather than the root. So I had to copy the data from /home/user/.fetchmailrc to /etc/fetchmailrc. Once that was done, the mails seemed to drop in correctly.

    Openoffice read my rotas that I put together in word correctly. I saved the latest version as an rtf and htm for distribution, rather than doc.

    Worryingly, file access seems to be stalled. Accessing the root folder or simple tasks like deleting file seem to take an unnecessarily long time.

    I also managed to get the HP Laserjet 1100 through the Intel Netport Express working by using a hybrid of editing the hosts file and printing directly via IP to the print server.

    It’s been a long day, but I’m gradually getting things sorted. There’s plenty more ahead though :(