transmission-daemon failing on Debian Jessie

Posted in General on Saturday, August 2, 2014 by Yatta

I’m trying to setup flexget with transmission but it was failing for some reason.


Setting up transmission-daemon (2.82-1.1+b1) …
Job for transmission-daemon.service failed. See ‘systemctl status transmission-daemon.service’ and ‘journalctl -xn’ for details.
invoke-rc.d: initscript transmission-daemon, action “start” failed.
dpkg: error processing package transmission-daemon (–configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)


Once I followed the below post from debian bug forum transmission-daemon started to no problem


usermod debian-transmission -d /var/lib/transmission-daemon

mkdir -p /var/lib/transmission-daemon/.config/transmission-daemon

mv /var/lib/transmission-daemon/info/*

rmdir info

ln -s /var/lib/transmission-daemon/.config/transmission-daemon

chown -R debian-transmission:debian-transmission
/var/lib/transmission-daemon /var/lib/transmission-daemon/.config



ksenior@roamer:~$ transmission-daemon -f

[22:45:44.162] Transmission 2.82 (14160) started (session.c:738)

[22:45:44.162] RPC Server Adding address to whitelist: (rpc-server.c:828)

[22:45:44.162] RPC Server Serving RPC and Web requests on port (rpc-server.c:1035)

[22:45:44.162] RPC Server Whitelist enabled (rpc-server.c:1039)

[22:45:44.162] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:78)

[22:45:44.162] UDP Please add the line “net.core.rmem_max = 4194304” to /etc/sysctl.conf (tr-udp.c:83)

[22:45:44.162] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:89)

[22:45:44.162] UDP Please add the line “net.core.wmem_max = 1048576” to /etc/sysctl.conf (tr-udp.c:94)

[22:45:44.162] DHT Generating new id (tr-dht.c:310)

[22:45:44.162] Using settings from “/home/ksenior/.config/transmission-daemon” (daemon.c:526)





 I had to modify /etc/sysctl.conf

root@roamer:~# vi /etc/sysctl.conf

add the lines noted in the error log

UDP Please add the line “net.core.rmem_max = 4194304” to /etc/sysctl.conf (tr-udp.c:83)

UDP Please add the line “net.core.wmem_max = 1048576” to /etc/sysctl.conf


To restart:

root@roamer:~# sysctl -p /etc/sysctl.conf

net.core.rmem_max = 4194304

net.core.wmem_max = 1048576




Vmware running on 2.6.35 Sid (aptosid)

Posted in General with tags , , , , on Saturday, September 18, 2010 by Yatta

Ok… Since they got rid of sidux decided to upgrade to the now aptosid (no better name????) Just like before after a new kernel install things are changed up. After a few searches on google I found a fix. (yea the previous fix no longer worked with this one)

thanks to (Nagilum)

cd /tmp
tar xvf /usr/lib/vmware/modules/source/vmmon.tar -C /tmp
perl -pi -e 's,_range,,' vmmon-only/linux/iommu.c
sudo tar cvf /usr/lib/vmware/modules/source/vmmon.tar vmmon-only

and fix some includes of course (this is basically the previous fix):

cd /lib/modules/$(uname -r)/build/include/linux && \
sudo find ../generated/ -type f -exec ln -s {} \;


I’m noticing with some of the newer kernels on my sidux (now aptosid… hate this new name) i have to download linux headers for the new kernel. After every dist-upgrade i have to follow it up with:

sudo apt-get install  linux-headers-$(uname -r)

Then I proceed to fix the various includes.

Compile vmware Workstation 7 Kernel 2.6.33 and

Posted in General on Tuesday, April 6, 2010 by Yatta

My vmware was working great from previous kernels… I updated my sid box to 2.6.33. Once I did that vmware would normally state that it needs to compile some stuff blah blah… With 2.6.33 it could not find some files… it seems like 2.6.33 changes up a little where it places some of the kernel header information.

cd /usr/src/linux-headers-2.6.33-2.slh.1-sidux-686/include/linux# ln -s ../generated/utsrelease.h

cd /usr/src/linux-headers-2.6.33-2.slh.1-sidux-686/include/linux# ln -s ../generated/autoconf.h .

Once the symbol links were created VOILA…. I’m able to run my vmware with this latest kernel. I got this help from HERE

VLC 1.0.5 via source in Lenny

Posted in General with tags , , on Sunday, March 14, 2010 by Yatta

I’ve installed Lenny on Bertha (HP XW4200) to basically be my multimedia pc…. having most of my saved tvshows, anime and maybe PVR (not sure yet)

I’ve wanted to add to this blog for sometime… but to he honest just been to rass lazy to do a writeup.

Anyway let’s get going with the reason for this post. VLC has always been a simple media player 0.8 is SIMPLE!!!! It was killing me.. i missed my vlc goldeneye!

1. I removed all aspects of vlc

apt-get –purge remove vlc

2. Since i’m going to install via source i need build-essentials

apt-get install build-essential

3. Now i tried to satisfy all the development dependencies

apt-get install libqt4-dev libpostproc-dev libavformat-dev libavcodec-dev libavutil-dev libmad0-dev liba52-0.7.4-dev libhal-dev libdbus-1-dev libfribidi-dev libgcrypt11-dev

I also had to install libx11-dev libxpm-dev x11proto-xext-dev libxext-dev

4. Get the source file from here .

tar -jxvf vlc-1.0.5.tar.bz2

5. Compile then install

./configure –disable-swscale –disable-nls –disable-mozilla

If i never added –disable-nls –disable-mozilla i would of ended up with

configure: error: Buggy GNU/libc (version 2.5 - 2.7) present. VLC would crash; there is no viable work-around for this. Check with your distribution vendor on how to update the glibc run-time.

Adding the 2 above options gets me through.


I get this error while trying to compile
/usr/bin/ld: cannot find -lGL

So I had t make a symbolic link

cd /usr/lib

ln -s

Then ran the make again…

sudo make install

BAM!!!! vlc 1.0.5 installed!!

Welcome home VLC …. sigh

Been Awhile

Posted in General on Sunday, October 4, 2009 by Yatta

Wow… well over a year… since my last blog?!?! Ohh well.

I’m setting back my MythTV box… but i need to share some files across my little network.Since i have nix boxes i figured I would set up a NFS share. I’ll set up a samba share also for those times i need to share files with a windows machine.

NFS Server

On the server:

apt-get install nfs-kernel-server nfs-common portmap

then vi /etc/exports


I chose the 192.168.x.x format to allow anyone on that particular network access to my NFS shares.

By using no_root_squash we tell NFS access should be made as root.. why you say? Mainly because I also want to be able to write to the direcctory (if our /home share was read-only, this wouldn’t be necessary).

Whenever /etc/exports is modified, we have to run

exportfs -a

to make the changes effective.

NFS Client

First I created the directories where I wanted to mount the NFS shares, e.g.:

mkdir -p /media/nfs/winstorage/
mkdir -p /media/nfs/deposit
mkdir -p /media/nfs/tvshows

To test it out I decided to mount my exported folders 🙂

mount /media/nfs/tvshowsmkdir -p /mnt/nfs/home

No Love 😦 I received the below error:

mount: wrong fs type, bad option, bad superblock on,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount.<type> helper program)
In some cases useful info is found in syslog – try
dmesg | tail  or so

i noticed I forgot to install nfs and port map stuff on my client… DUH!!!

apt-get install portmap nfs-common

Afterwards, we can mount them as follows:

enigma@andromeda:~$ mount /media/nfs/tvshows

No Error!!! Yippe!!!

Hardy is it worth it?

Posted in Computers & Internet, Linux on Wednesday, July 30, 2008 by Yatta

I’ve upgraded my desktop to Ubuntu Hardy Heron the day it was released no big issues there. So last week I decided to upgrade my Dell D820 work laptop to Hardy… fllllaaawwweeddd plan!! If it’s not the annoying system beep it’s program freezing for now apparent reason. Your special function keys just stop working (you have ANY idea how hard it is to work on some machines without your special keys for eg. caps).

This keyboard thing though seems to be contributed to having VMware installed on your computer. The CTRL, ALT, Shift, etc. keys will stop working on the host machine but will continue to work in the VM machine. After doing some searching I found out that if you run:
You get your stuff back after you type that in. Granted at times you may have to type it in a few times but that is better than rebooting your damn machine.

UUID… Is it really better?

Posted in General on Monday, May 5, 2008 by Yatta

Ubuntu started using UUID’s from around Edgy Eft I believe. I must
admit though when I upgraded to Edgy. I noticed the change to UUID in
my /etc/fstab but I never paid it any mind; “If it ain’t broke don’t
fix it!!”. I’ve since did a network upgrade to Hardy from Gutsy… that
‘install’ messed up my partitions 😦 !!!!!

First let me give you the wikipedia definition of UUID:

The intent of UUIDs is to enable distributed systems to uniquely
identify information without significant central coordination. Thus,
anyone can create a UUID and use it to identify something with
reasonable confidence that the identifier will never be unintentionally
used by anyone for anything else.

UUID is good for people who use alot of removable devices.By using UUID you  don’t have to worry about disk label issues. While normal desktop users who don’t really change or add hard drives to their up an running system will see UUID as just more headache in the *nix world.
Not sure where I picked up this info from but this is put as simply as possible I believe:

No matter if you change how the hd is connected to your system (for example primary/secondary master/slave for IDE) the UUID never changes, whereas the device node can change. Thus the association between mount point and partition is more robust when using UUIDs.

Which do you prefer:

UUID=855c621e-cc8b-4a2c-9b22-e01aa751b870    /media/layover    ext3     defaults           0          2


/dev/sda5 /media/unno ext3 defaults 0 2

If you are interested in finding out what your UUID is for a particular partition type:

sudo vol_id -u device