Jump to content
flixxx

Howto: install rtorrent running in a screen session.

26 posts in this topic Last Reply

Recommended Posts

Someone requested an updated tutorial.

 

It currently works with Unraid version 5. This is rtorrent 0.8.9

I can't offer much support, but i'll do my best.

 

Step 1

 

Unzip the following files onto your USB flash drive in the "packages" folder. Create one if it doesn't exist;

 

https://dl.dropbox.com/u/8439332/rtorrent.zip

https://dl.dropbox.com/u/8439332/screen.zip

 

File structure should look like this;

 

Flash:/packages/screen

|-ncurses-5.6-i486-3.tgz

|-screen-4.0.3-i486-1.tgz

|-utempter-1.1.4-i486-1.tgz

 

Flash:/packages/rtorrent

|-curl-7.19.6-i486-1_slack12.2.tgz

|-libidn-1.5-i486-1.tgz

|-libsigc++-2.2.8-i486-1mfb.txz

|-libtorrent-0.12.9-i486-1_SBo.tgz

|-rtorrent-0.8.9-i486-1_SBo.tgz

|-xmlrpc-c-1.11.00-i486-1.tgz

 

Step 2

 

Add this to your go file:

 

#######################TORRENT INSTALLATION##############################

 

#Install Screen

mkdir /var/log/wtmp

installpkg /boot/packages/screen/*

 

#Install rtorrent

installpkg /boot/packages/rtorrent/*

 

#Removing locked rtorrent from session in case of bad reboot

rm /mnt/www/session/rtorrent.lock

 

#Starting rtorrent

/usr/bin/screen -dmS rtorrent su -c '/usr/bin/rtorrent -n -o import=/boot/rtorrent.rc' nobody

 

#Create symbolic link for .screen

ln -s /.screen /root/

 

#undefining

stty start undef

 

#Kill rtorrent on server stop

sed -i  "/to stop network services./a pkill -2 rtorrent" /usr/local/sbin/emhttp_event

 

#######################TORRENT INSTALLATION END##########################

 

Step 3

 

Create a rtorrent.rc file, here is a sample: http://libtorrent.rakshasa.no/browser/trunk/rtorrent/doc/rtorrent.rc?rev=latest

 

Step 4

 

Place the rtorrent.rc file in the root of your flash.

 

Step 5

 

I strongly recommend that your rtorrent.rc file contains a session path. (in sample #session = ./session). The session path saves the torrents, after a reboot your sessions will resume.

The session folder can be anywhere on your physical hard drive as long as the folder is already created. You will also have to edit the item in red above (In your go script) to reflect the folder.

 

For example, say you want the session folder to be in a hidden folder on your cache drive, you will do the following;

 

Create the folder

mkdir /mnt/cache/.session

 

edit rtorrent.rc

#session = ./session

to

session = /mnt/cache/.session

 

edit this section of the go folder;

 

rm /mnt/www/session/rtorrent.lock

to

rm /mnt/cache/.session/rtorrent.lock

 

That is all.

 

Rutorrent tutorial will follow this one shortly...

Share this post


Link to post

@flixxx

 

You da Man!!!

 

Although I'm half way through setting up with your tutorial (before the wife interrupted(read: Nag nag) me), I was wondering if I can use the rtorrent.rc from bubbaqraid?

 

I do like his folder structure, but just want to check any settings he has in it are still compliant with the latest rtorrent.

 

# This is the resource file for rTorrent. 
# BubbaRaid expects this file to be in /root/.rtorrent.rc
#
# Based on original .rtorrent.rc file from http://libtorrent.rakshasa.no/
# Modified by Bubba for BubbaRaid
#
# This assumes the following directory structure:
# 
# /mnt/disk1/torrents/downloading - Temporaray location for torrents while downloading (see "directory")
# /mnt/disk1/torrents/complete      - Torrents are moved here when complete (see "on_finished")
# /mnt/disk1/torrents/auto             - The 'autoload' directory for rtorrent to use.  Place a file 
#                                                    in here, and rtorrent loads it automatically.
#
# /mnt/disk1/torrents/downloading/rtorrent.session - for storing rtorrent session information
#

# Maximum and minimum number of peers to connect to per torrent.
#min_peers = 40
#max_peers = 100

# Same as above but for seeding completed torrents (-1 = same as downloading)
#min_peers_seed = 10
#max_peers_seed = 50

# Maximum number of simultanious uploads per torrent.
#max_uploads = 15

# Global upload and download rate in KiB. "0" for unlimited.
#download_rate = 0
#upload_rate = 50

# Default directory to save the downloaded torrents.
directory = /mnt/disk1/torrents/downloading

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = /mnt/disk1/torrents/downloading/rtorrent.session

# Watch a directory for new torrents, and stop those that have been
# deleted.
schedule = watch_directory,5,5,load_start=/mnt/disk1/torrents/auto/*.torrent
schedule = untied_directory,5,5,stop_untied=

# Close torrents when diskspace is low. */
#schedule = low_diskspace,5,60,close_low_diskspace=100M

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.
# example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0
#schedule = ratio,60,60,stop_on_ratio=200,200M,2000

execute_log = /var/log/rtorrent.log

# When the torrent finishes, it executes "mv -n <base_path> ~/Download/"
# and then sets the destination directory to "~/Download/". (0.7.7 )
on_finished = move_complete,"execute=mv,-u,$d.get_base_path=,/mnt/disk1/torrents/complete/ .set_directory=/mnt/disk1/torrents/complete/"

# The ip address reported to the tracker.
#ip = 127.0.0.1
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
port_range = 6890-6999

# Set up XMLRPC port same as in lighttpd config
scgi_port = 127.0.0.1:5000

# Start opening ports at a random position within the port range.
#port_random = no

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
#check_hash = no

# Set whetever the client should try to connect to UDP trackers.
use_udp_trackers = yes

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
encryption = allow_incoming,enable_retry,prefer_plaintext

#
# Do not modify the following parameters unless you know what you're doing.
#

# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10

# Max number of files to keep open simultaniously.
#max_open_files = 128

# Number of sockets to simultaneously keep open.
#max_open_sockets = <no default>


# Example of scheduling commands: Switch between two ip's every 5
# seconds.
#schedule = "ip_tick1,5,10,ip=torretta"
#schedule = "ip_tick2,10,10,ip=lampedusa"

# Remove a scheduled event.
#schedule_remove = "ip_tick1"

 

I see where I may have gone wrong, with configuring  unweb's lighttpd, it wouldn't stick, then I got a 500 error in firefox.

 

As per your post http://lime-technology.com/forum/index.php?topic=4303.msg38089#msg38089 you also mentioned

Now I took it one step further becasue my webserver has nothing else in it, so instead of goinmg to "http://tower:83/rutorrent" i just go directly to http://tower:83. If you'd like to achieve the same thing just type:

 

Code:

 

mv /mnt/disk1/wwwdocs/rutorrent/* /mnt/disk1/wwwdocs/

rm -r /mnt/disk1/wwwdocs/rutorrent

 

This is still a valid option?

 

I should be able to complete this tonight for sure.

 

Much Appreciated! :D

Share this post


Link to post

@flixxx

 

You da Man!!!

 

Although I'm half way through setting up with your tutorial (before the wife interrupted(read: Nag nag) me), I was wondering if I can use the rtorrent.rc from bubbaqraid?

 

I do like his folder structure, but just want to check any settings he has in it are still compliant with the latest rtorrent.

 

# This is the resource file for rTorrent. 
# BubbaRaid expects this file to be in /root/.rtorrent.rc
#
# Based on original .rtorrent.rc file from http://libtorrent.rakshasa.no/
# Modified by Bubba for BubbaRaid
#
# This assumes the following directory structure:
# 
# /mnt/disk1/torrents/downloading - Temporaray location for torrents while downloading (see "directory")
# /mnt/disk1/torrents/complete      - Torrents are moved here when complete (see "on_finished")
# /mnt/disk1/torrents/auto             - The 'autoload' directory for rtorrent to use.  Place a file 
#                                                    in here, and rtorrent loads it automatically.
#
# /mnt/disk1/torrents/downloading/rtorrent.session - for storing rtorrent session information
#

# Maximum and minimum number of peers to connect to per torrent.
#min_peers = 40
#max_peers = 100

# Same as above but for seeding completed torrents (-1 = same as downloading)
#min_peers_seed = 10
#max_peers_seed = 50

# Maximum number of simultanious uploads per torrent.
#max_uploads = 15

# Global upload and download rate in KiB. "0" for unlimited.
#download_rate = 0
#upload_rate = 50

# Default directory to save the downloaded torrents.
directory = /mnt/disk1/torrents/downloading

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = /mnt/disk1/torrents/downloading/rtorrent.session

# Watch a directory for new torrents, and stop those that have been
# deleted.
schedule = watch_directory,5,5,load_start=/mnt/disk1/torrents/auto/*.torrent
schedule = untied_directory,5,5,stop_untied=

# Close torrents when diskspace is low. */
#schedule = low_diskspace,5,60,close_low_diskspace=100M

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.
# example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0
#schedule = ratio,60,60,stop_on_ratio=200,200M,2000

execute_log = /var/log/rtorrent.log

# When the torrent finishes, it executes "mv -n <base_path> ~/Download/"
# and then sets the destination directory to "~/Download/". (0.7.7 )
on_finished = move_complete,"execute=mv,-u,$d.get_base_path=,/mnt/disk1/torrents/complete/ .set_directory=/mnt/disk1/torrents/complete/"

# The ip address reported to the tracker.
#ip = 127.0.0.1
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
port_range = 6890-6999

# Set up XMLRPC port same as in lighttpd config
scgi_port = 127.0.0.1:5000

# Start opening ports at a random position within the port range.
#port_random = no

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
#check_hash = no

# Set whetever the client should try to connect to UDP trackers.
use_udp_trackers = yes

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
encryption = allow_incoming,enable_retry,prefer_plaintext

#
# Do not modify the following parameters unless you know what you're doing.
#

# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10

# Max number of files to keep open simultaniously.
#max_open_files = 128

# Number of sockets to simultaneously keep open.
#max_open_sockets = <no default>


# Example of scheduling commands: Switch between two ip's every 5
# seconds.
#schedule = "ip_tick1,5,10,ip=torretta"
#schedule = "ip_tick2,10,10,ip=lampedusa"

# Remove a scheduled event.
#schedule_remove = "ip_tick1"

 

I see where I may have gone wrong, with configuring  unweb's lighttpd, it wouldn't stick, then I got a 500 error in firefox.

 

As per your post http://lime-technology.com/forum/index.php?topic=4303.msg38089#msg38089 you also mentioned

Now I took it one step further becasue my webserver has nothing else in it, so instead of goinmg to "http://tower:83/rutorrent" i just go directly to http://tower:83. If you'd like to achieve the same thing just type:

 

Code:

 

mv /mnt/disk1/wwwdocs/rutorrent/* /mnt/disk1/wwwdocs/

rm -r /mnt/disk1/wwwdocs/rutorrent

 

This is still a valid option?

 

I should be able to complete this tonight for sure.

 

Much Appreciated! :D

 

Hi Phoenix, you can put the RUtorrent content in the root of the webserver if you'd like.

 

Based on Bubbaraid's rtorrent file, it seems like you will need a sessions folder, complete folder, downloads folder and watch folder. as long as you have them already created it will not be a problem.

 

Great work flixxx! Looks your experimenting has paid off :P

 

Thanks Boof, I just installed slackware 13.0 on a VM, i'm hoping to create a new rtorrent and libtorrent package. I'll message you if I hit any roadblocks ;)

Share this post


Link to post

OK, quick play this morning, and I at least got the rutorrent to fire up on port 86.

 

Two things I had to do first, was check 'lighttpd.conf.include'.  I found that it cut off the directory I had rutorrent extracted.  It had it listed as 'mnt/disk1/www' when I had typed in 'mnt/disk1/wwwdocs'.

 

Second change was I followed your instructions to move rutorrent files from it's extracted folder into wwwdocs.  Re-reading afterwards found the folders were named differently.

mv /mnt/disk1/wwwdocs/rutorrent/* /mnt/disk1/wwwdocs/
rm -r /mnt/disk1/wwwdocs/rutorrent

 

My Folder after was rtorrent, not rutorrent.

 

OK, so got the web interface up and working after a reboot (finding my GigaNic not always coming on after reboots, might upgrade to latest beta), to find error message in rutorrent, something about rtorrent not started or not started correctly.

 

Now, I figure its all to do with the rtorrent.rc file.  reading and re-reading, I see sometimes people mention the file should be '.rtorrent.rc', other times just 'rtorrent.rc'.  note the extra '.' in front of the filename.  SO, which is correct.  IF I try and edit the file in windows it says something about no filename listed before the extension.

 

minor guidance required. :P

Share this post


Link to post

OK, quick play this morning, and I at least got the rutorrent to fire up on port 86.

 

Two things I had to do first, was check 'lighttpd.conf.include'.  I found that it cut off the directory I had rutorrent extracted.  It had it listed as 'mnt/disk1/www' when I had typed in 'mnt/disk1/wwwdocs'.

 

Second change was I followed your instructions to move rutorrent files from it's extracted folder into wwwdocs.  Re-reading afterwards found the folders were named differently.

mv /mnt/disk1/wwwdocs/rutorrent/* /mnt/disk1/wwwdocs/
rm -r /mnt/disk1/wwwdocs/rutorrent

 

My Folder after was rtorrent, not rutorrent.

 

OK, so got the web interface up and working after a reboot (finding my GigaNic not always coming on after reboots, might upgrade to latest beta), to find error message in rutorrent, something about rtorrent not started or not started correctly.

 

Now, I figure its all to do with the rtorrent.rc file.  reading and re-reading, I see sometimes people mention the file should be '.rtorrent.rc', other times just 'rtorrent.rc'.  note the extra '.' in front of the filename.  SO, which is correct.  IF I try and edit the file in windows it says something about no filename listed before the extension.

 

minor guidance required. :P

 

the error states that rtorrent is not started. rtorrent.rc or .rtorrent.rc won't make a difference, just make sure in your go when you have screen -dmS rtorrent -n -o import=/boot/custom/etc/rtorrent.rc(or .rtorrent.rc)  the "." just makes the file hidden.

 

you can put the rtorrent file wherever u want really, the above post is just a guideline, make sure you put the correct path and filename in the go script for "import"

 

Anyway, after you reboot. give it a little extra time (about another 2-3 minutes) and telnet into the box. type "screen -ls", this iwll give you all the instances of screen started... you should have one.

Share this post


Link to post

YIPPIE!!! ;D ;D ;D ;D ;D

 

One Happy Camper!! :o

 

All seems to be working well.  Not sure if the private tracker part is working but will check that out in the next couple of days.

 

It's working! 

 

OK, now how do I do a clean shutdown of rtorrent.  I read somewhere about a shutdown script or something, I'll find the right forum, but what do I need to add into it to close rtorrent cleanly?

 

Many Thanks for the tutorial.  My slight glitches aside, I am very happy.  Thank you! ;)

Share this post


Link to post

This is something I was wondering about for unRaid. I'm going to give this a try this weekend. What does the "screen" package do? I run my system headless.

 

Thank you for the writeup.

Share this post


Link to post

This is something I was wondering about for unRaid. I'm going to give this a try this weekend. What does the "screen" package do? I run my system headless.

 

Thank you for the writeup.

 

screen is a virtual terminal that keeps running in the background. If you're running it headless, you'll definitely need this. You can get more information here:

 

http://www.manpagez.com/man/1/screen/

Share this post


Link to post

OK, I may have jumped for joy too soon.

 

getting this message in rutorrent after leaving it for over 5 minutes.

[10.12.2009 18:19:10] WebUI started.
[10.12.2009 18:19:10] Bad link to rTorrent. Check if it is really running. Check $scgi_port and $scgi_host settings in config.php and scgi_port in rTorrent configuration file.
[10.12.2009 18:19:11] Bad response: (500) <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>500 - Internal Server Error</title> </head> <body> <h1>500 - Internal Server Error</h1> </body> </html> 

 

 

Also found an error.log in /var/log/lighttpd

2009-12-10 18:11:36: (log.c.75) server started 
2009-12-10 18:18:56: (mod_scgi.c.2222) establishing connection failed: Connection refused 
2009-12-10 18:18:56: (mod_scgi.c.2356) fcgi-server disabled: 127.0.0.1 5000  
2009-12-10 18:18:56: (mod_scgi.c.2825) no fcgi-handler found for: /RPC2 
2009-12-10 18:19:57: (mod_scgi.c.2050) fcgi-server re-enabled: 127.0.0.1 5000  
2009-12-10 18:41:18: (mod_scgi.c.2222) establishing connection failed: Connection refused 
2009-12-10 18:41:18: (mod_scgi.c.2356) fcgi-server disabled: 127.0.0.1 5000  
2009-12-10 18:41:18: (mod_scgi.c.2825) no fcgi-handler found for: /RPC2 
2009-12-10 18:41:22: (mod_scgi.c.2825) no fcgi-handler found for: /RPC2 
2009-12-10 18:42:19: (mod_scgi.c.2050) fcgi-server re-enabled: 127.0.0.1 5000 

 

Help!  Any other logs that may be of help?

Share this post


Link to post

And here is my half my syslog.  anyone able to see a problem with it?

Dec 10 18:11:27 Tower syslogd 1.4.1: restart.
Dec 10 18:11:27 Tower kernel: klogd 1.4.1, log source = /proc/kmsg started.
Dec 10 18:11:27 Tower kernel: Linux version 2.6.31.6-unRAID (root@Develop) (gcc version 4.2.3) #6 SMP Thu Dec 3 10:00:15 MST 2009
Dec 10 18:11:27 Tower kernel: KERNEL supported cpus:
Dec 10 18:11:27 Tower kernel:   Intel GenuineIntel
Dec 10 18:11:27 Tower kernel:   AMD AuthenticAMD
Dec 10 18:11:27 Tower kernel:   NSC Geode by NSC
Dec 10 18:11:27 Tower kernel:   Cyrix CyrixInstead
Dec 10 18:11:27 Tower kernel:   Centaur CentaurHauls
Dec 10 18:11:27 Tower kernel:   Transmeta GenuineTMx86
Dec 10 18:11:27 Tower kernel:   Transmeta TransmetaCPU
Dec 10 18:11:27 Tower kernel:   UMC UMC UMC UMC
Dec 10 18:11:27 Tower kernel: BIOS-provided physical RAM map:
Dec 10 18:11:27 Tower kernel:  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Dec 10 18:11:27 Tower kernel:  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Dec 10 18:11:27 Tower kernel:  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Dec 10 18:11:27 Tower kernel:  BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
Dec 10 18:11:27 Tower kernel:  BIOS-e820: 000000000fff0000 - 000000000fff3000 (ACPI NVS)
Dec 10 18:11:27 Tower kernel:  BIOS-e820: 000000000fff3000 - 0000000010000000 (ACPI data)
Dec 10 18:11:27 Tower kernel:  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Dec 10 18:11:27 Tower kernel:  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Dec 10 18:11:27 Tower kernel:  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Dec 10 18:11:27 Tower kernel: DMI 2.2 present.
Dec 10 18:11:27 Tower kernel: Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
Dec 10 18:11:27 Tower kernel: e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Dec 10 18:11:27 Tower kernel: last_pfn = 0xfff0 max_arch_pfn = 0x1000000
Dec 10 18:11:27 Tower kernel: MTRR default type: uncachable
Dec 10 18:11:27 Tower kernel: MTRR fixed ranges enabled:
Dec 10 18:11:27 Tower kernel:   00000-9FFFF write-back
Dec 10 18:11:27 Tower kernel:   A0000-BFFFF uncachable
Dec 10 18:11:27 Tower kernel:   C0000-C7FFF write-protect
Dec 10 18:11:27 Tower kernel:   C8000-FFFFF uncachable
Dec 10 18:11:27 Tower kernel: MTRR variable ranges enabled:
Dec 10 18:11:27 Tower kernel:   0 base 000000000 mask FF0000000 write-back
Dec 10 18:11:27 Tower kernel:   1 base 0D0000000 mask FF8000000 write-combining
Dec 10 18:11:27 Tower kernel:   2 base 0D0000000 mask FF8000000 write-combining
Dec 10 18:11:27 Tower kernel:   3 disabled
Dec 10 18:11:27 Tower kernel:   4 disabled
Dec 10 18:11:27 Tower kernel:   5 disabled
Dec 10 18:11:27 Tower kernel:   6 disabled
Dec 10 18:11:27 Tower kernel:   7 disabled
Dec 10 18:11:27 Tower kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Dec 10 18:11:27 Tower kernel: initial memory mapped : 0 - 01800000
Dec 10 18:11:27 Tower kernel: init_memory_mapping: 0000000000000000-000000000fff0000
Dec 10 18:11:27 Tower kernel:  0000000000 - 0000200000 page 4k
Dec 10 18:11:27 Tower kernel:  0000200000 - 000fe00000 page 2M
Dec 10 18:11:27 Tower kernel:  000fe00000 - 000fff0000 page 4k
Dec 10 18:11:27 Tower kernel: kernel direct mapping tables up to fff0000 @ 10000-16000
Dec 10 18:11:27 Tower kernel: RAMDISK: 0cd7f000 - 0ffefbef
Dec 10 18:11:27 Tower kernel: ACPI: RSDP 000f6fa0 00014 (v00 VKT400)
Dec 10 18:11:27 Tower kernel: ACPI: RSDT 0fff3000 0002C (v01 VKT400 AWRDACPI 42302E31 AWRD 00000000)
Dec 10 18:11:27 Tower kernel: ACPI: FACP 0fff3040 00074 (v01 VKT400 AWRDACPI 42302E31 AWRD 00000000)
Dec 10 18:11:27 Tower kernel: ACPI: DSDT 0fff30c0 03DD0 (v01 VKT400 AWRDACPI 00001000 MSFT 0100000D)
Dec 10 18:11:27 Tower kernel: ACPI: FACS 0fff0000 00040
Dec 10 18:11:27 Tower kernel: ACPI: APIC 0fff6ec0 00054 (v01 VKT400 AWRDACPI 42302E31 AWRD 00000000)
Dec 10 18:11:27 Tower kernel: ACPI: Local APIC address 0xfee00000
Dec 10 18:11:27 Tower kernel: 0MB HIGHMEM available.
Dec 10 18:11:27 Tower kernel: 255MB LOWMEM available.
Dec 10 18:11:27 Tower kernel:   mapped low ram: 0 - 0fff0000
Dec 10 18:11:27 Tower kernel:   low ram: 0 - 0fff0000
Dec 10 18:11:27 Tower kernel:   node 0 low ram: 00000000 - 0fff0000
Dec 10 18:11:27 Tower kernel:   node 0 bootmap 00012000 - 00014000
Dec 10 18:11:27 Tower kernel: (9 early reservations) ==> bootmem [0000000000 - 000fff0000]
Dec 10 18:11:27 Tower kernel:   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
Dec 10 18:11:27 Tower kernel:   #1 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 - 0000002000]
Dec 10 18:11:27 Tower kernel:   #2 [0000006000 - 0000007000]       TRAMPOLINE ==> [0000006000 - 0000007000]
Dec 10 18:11:27 Tower kernel:   #3 [0001000000 - 0001460788]    TEXT DATA BSS ==> [0001000000 - 0001460788]
Dec 10 18:11:27 Tower kernel:   #4 [000cd7f000 - 000ffefbef]          RAMDISK ==> [000cd7f000 - 000ffefbef]
Dec 10 18:11:27 Tower kernel:   #5 [000009fc00 - 0000100000]    BIOS reserved ==> [000009fc00 - 0000100000]
Dec 10 18:11:27 Tower kernel:   #6 [0001461000 - 000146d0ae]              BRK ==> [0001461000 - 000146d0ae]
Dec 10 18:11:27 Tower kernel:   #7 [0000010000 - 0000012000]          PGTABLE ==> [0000010000 - 0000012000]
Dec 10 18:11:27 Tower kernel:   #8 [0000012000 - 0000014000]          BOOTMAP ==> [0000012000 - 0000014000]
Dec 10 18:11:27 Tower kernel: found SMP MP-table at [c00f54c0] f54c0
Dec 10 18:11:27 Tower kernel: Zone PFN ranges:
Dec 10 18:11:27 Tower kernel:   DMA      0x00000010 -> 0x00001000
Dec 10 18:11:27 Tower kernel:   Normal   0x00001000 -> 0x0000fff0
Dec 10 18:11:27 Tower kernel:   HighMem  0x0000fff0 -> 0x0000fff0
Dec 10 18:11:27 Tower kernel: Movable zone start PFN for each node
Dec 10 18:11:27 Tower kernel: early_node_map[2] active PFN ranges
Dec 10 18:11:27 Tower kernel:     0: 0x00000010 -> 0x0000009f
Dec 10 18:11:27 Tower kernel:     0: 0x00000100 -> 0x0000fff0
Dec 10 18:11:27 Tower kernel: On node 0 totalpages: 65407
Dec 10 18:11:27 Tower kernel: free_area_init_node: node 0, pgdat c13d4940, node_mem_map c146e200
Dec 10 18:11:27 Tower kernel:   DMA zone: 32 pages used for memmap
Dec 10 18:11:27 Tower kernel:   DMA zone: 0 pages reserved
Dec 10 18:11:27 Tower kernel:   DMA zone: 3951 pages, LIFO batch:0
Dec 10 18:11:27 Tower kernel:   Normal zone: 480 pages used for memmap
Dec 10 18:11:27 Tower kernel:   Normal zone: 60944 pages, LIFO batch:15
Dec 10 18:11:27 Tower kernel: Using APIC driver default
Dec 10 18:11:27 Tower kernel: ACPI: PM-Timer IO Port: 0x4008
Dec 10 18:11:27 Tower kernel: ACPI: Local APIC address 0xfee00000
Dec 10 18:11:27 Tower kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Dec 10 18:11:27 Tower kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Dec 10 18:11:27 Tower kernel: IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
Dec 10 18:11:27 Tower kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Dec 10 18:11:27 Tower kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 dfl dfl)
Dec 10 18:11:27 Tower kernel: ACPI: IRQ0 used by override.
Dec 10 18:11:27 Tower kernel: ACPI: IRQ2 used by override.
Dec 10 18:11:27 Tower kernel: ACPI: IRQ9 used by override.
Dec 10 18:11:27 Tower kernel: Enabling APIC mode:  Flat.  Using 1 I/O APICs
Dec 10 18:11:27 Tower kernel: Using ACPI (MADT) for SMP configuration information
Dec 10 18:11:27 Tower kernel: SMP: Allowing 1 CPUs, 0 hotplug CPUs
Dec 10 18:11:27 Tower kernel: nr_irqs_gsi: 24
Dec 10 18:11:27 Tower kernel: Allocating PCI resources starting at 10000000 (gap: 10000000:eec00000)
Dec 10 18:11:27 Tower kernel: NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:1 nr_node_ids:1
Dec 10 18:11:27 Tower kernel: PERCPU: Embedded 11 pages at c1670000, static data 21980 bytes
Dec 10 18:11:27 Tower kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 64895
Dec 10 18:11:27 Tower kernel: Kernel command line: initrd=bzroot BOOT_IMAGE=bzimage 
Dec 10 18:11:27 Tower kernel: PID hash table entries: 1024 (order: 10, 4096 bytes)
Dec 10 18:11:27 Tower kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Dec 10 18:11:27 Tower kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Dec 10 18:11:27 Tower kernel: Enabling fast FPU save and restore... done.
Dec 10 18:11:27 Tower kernel: Enabling unmasked SIMD FPU exception support... done.
Dec 10 18:11:27 Tower kernel: Initializing CPU#0
Dec 10 18:11:27 Tower kernel: Initializing HighMem for node 0 (00000000:00000000)
Dec 10 18:11:27 Tower kernel: Memory: 202912k/262080k available (2620k kernel code, 58516k reserved, 1316k data, 292k init, 0k highmem)
Dec 10 18:11:27 Tower kernel: virtual kernel memory layout:
Dec 10 18:11:27 Tower kernel:     fixmap  : 0xfff6b000 - 0xfffff000   ( 592 kB)
Dec 10 18:11:27 Tower kernel:     pkmap   : 0xffa00000 - 0xffc00000   (2048 kB)
Dec 10 18:11:27 Tower kernel:     vmalloc : 0xd07f0000 - 0xff9fe000   ( 754 MB)
Dec 10 18:11:27 Tower kernel:     lowmem  : 0xc0000000 - 0xcfff0000   ( 255 MB)
Dec 10 18:11:27 Tower kernel:       .init : 0xc13d9000 - 0xc1422000   ( 292 kB)
Dec 10 18:11:27 Tower kernel:       .data : 0xc128f0e5 - 0xc13d8454   (1316 kB)
Dec 10 18:11:27 Tower kernel:       .text : 0xc1000000 - 0xc128f0e5   (2620 kB)
Dec 10 18:11:27 Tower kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
Dec 10 18:11:27 Tower kernel: SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Dec 10 18:11:27 Tower kernel: NR_IRQS:384
Dec 10 18:11:27 Tower kernel: Fast TSC calibration using PIT
Dec 10 18:11:27 Tower kernel: Detected 1468.304 MHz processor.
Dec 10 18:11:27 Tower kernel: Console: colour VGA+ 80x25
Dec 10 18:11:27 Tower kernel: console [tty0] enabled
Dec 10 18:11:27 Tower kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 2936.60 BogoMIPS (lpj=14683040)
Dec 10 18:11:27 Tower kernel: Mount-cache hash table entries: 512
Dec 10 18:11:27 Tower kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Dec 10 18:11:27 Tower kernel: CPU: L2 Cache: 512K (64 bytes/line)
Dec 10 18:11:27 Tower kernel: mce: CPU supports 4 MCE banks
Dec 10 18:11:27 Tower kernel: Checking 'hlt' instruction... OK.
Dec 10 18:11:27 Tower kernel: SMP alternatives: switching to UP code
Dec 10 18:11:27 Tower kernel: Freeing SMP alternatives: 14k freed
Dec 10 18:11:27 Tower kernel: ACPI: Core revision 20090521
Dec 10 18:11:27 Tower kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Dec 10 18:11:27 Tower kernel: CPU0: AMD Athlon(tm) XP 1900+ stepping 00
Dec 10 18:11:27 Tower kernel: Brought up 1 CPUs
Dec 10 18:11:27 Tower kernel: Total of 1 processors activated (2936.60 BogoMIPS).
Dec 10 18:11:27 Tower kernel: NET: Registered protocol family 16
Dec 10 18:11:27 Tower kernel: ACPI: bus type pci registered
Dec 10 18:11:27 Tower kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb3e0, last bus=1
Dec 10 18:11:27 Tower kernel: PCI: Using configuration type 1 for base access
Dec 10 18:11:27 Tower kernel: bio: create slab <bio-0> at 0
Dec 10 18:11:27 Tower kernel: ACPI: EC: Look up EC in DSDT
Dec 10 18:11:27 Tower kernel: ACPI: Interpreter enabled
Dec 10 18:11:27 Tower kernel: ACPI: (supports S0 S1 S5)
Dec 10 18:11:27 Tower kernel: ACPI: Using IOAPIC for interrupt routing
Dec 10 18:11:27 Tower kernel: ACPI: No dock devices found.
Dec 10 18:11:27 Tower kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Dec 10 18:11:27 Tower kernel: pci 0000:00:00.0: reg 10 32bit mmio: [0xd0000000-0xd7ffffff]
Dec 10 18:11:27 Tower kernel: pci 0000:00:01.0: supports D1
Dec 10 18:11:27 Tower kernel: pci 0000:00:0c.0: reg 10 32bit mmio: [0xdc020000-0xdc023fff]
Dec 10 18:11:27 Tower kernel: pci 0000:00:0c.0: reg 14 io port: [0xd000-0xd0ff]
Dec 10 18:11:27 Tower kernel: pci 0000:00:0c.0: reg 30 32bit mmio: [0x000000-0x01ffff]
Dec 10 18:11:27 Tower kernel: pci 0000:00:0c.0: supports D1 D2
Dec 10 18:11:27 Tower kernel: pci 0000:00:0c.0: PME# supported from D0 D1 D2 D3hot D3cold
Dec 10 18:11:27 Tower kernel: pci 0000:00:0c.0: PME# disabled
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.0: reg 20 io port: [0xd400-0xd41f]
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.0: supports D1 D2
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.0: PME# supported from D0 D1 D2 D3hot D3cold
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.0: PME# disabled
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.1: reg 20 io port: [0xd800-0xd81f]
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.1: supports D1 D2
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.1: PME# supported from D0 D1 D2 D3hot D3cold
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.1: PME# disabled
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.2: reg 20 io port: [0xdc00-0xdc1f]
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.2: supports D1 D2
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.2: PME# supported from D0 D1 D2 D3hot D3cold
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.2: PME# disabled
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.3: reg 10 32bit mmio: [0xdc024000-0xdc0240ff]
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.3: supports D1 D2
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.3: PME# supported from D0 D1 D2 D3hot D3cold
Dec 10 18:11:27 Tower kernel: pci 0000:00:10.3: PME# disabled

Share this post


Link to post

Other half of my syslog

Dec 10 18:11:27 Tower kernel: HPET not enabled in BIOS. You might try hpet=force boot option
Dec 10 18:11:27 Tower kernel: pci 0000:00:11.0: quirk: region 4000-407f claimed by vt8235 PM
Dec 10 18:11:27 Tower kernel: pci 0000:00:11.0: quirk: region 5000-500f claimed by vt8235 SMB
Dec 10 18:11:27 Tower kernel: pci 0000:00:11.1: reg 20 io port: [0xe000-0xe00f]
Dec 10 18:11:27 Tower kernel: pci 0000:01:00.0: reg 10 32bit mmio: [0xda000000-0xdaffffff]
Dec 10 18:11:27 Tower kernel: pci 0000:01:00.0: reg 14 32bit mmio: [0xd8000000-0xd9ffffff]
Dec 10 18:11:27 Tower kernel: pci 0000:01:00.0: reg 30 32bit mmio: [0x000000-0x00ffff]
Dec 10 18:11:27 Tower kernel: pci 0000:00:01.0: bridge 32bit mmio: [0xda000000-0xdbffffff]
Dec 10 18:11:27 Tower kernel: pci 0000:00:01.0: bridge 32bit mmio pref: [0xd8000000-0xd9ffffff]
Dec 10 18:11:27 Tower kernel: pci_bus 0000:00: on NUMA node 0
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 *7 10 11 12 14 15)
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *0
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [ALKB] (IRQs 21) *0
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [ALKD] (IRQs 23) *0
Dec 10 18:11:27 Tower kernel: SCSI subsystem initialized
Dec 10 18:11:27 Tower kernel: libata version 3.00 loaded.
Dec 10 18:11:27 Tower kernel: usbcore: registered new interface driver usbfs
Dec 10 18:11:27 Tower kernel: usbcore: registered new interface driver hub
Dec 10 18:11:27 Tower kernel: usbcore: registered new device driver usb
Dec 10 18:11:27 Tower kernel: PCI: Using ACPI for IRQ routing
Dec 10 18:11:27 Tower kernel: pnp: PnP ACPI init
Dec 10 18:11:27 Tower kernel: ACPI: bus type pnp registered
Dec 10 18:11:27 Tower kernel: pnp: PnP ACPI: found 10 devices
Dec 10 18:11:27 Tower kernel: ACPI: ACPI bus type pnp unregistered
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0xd0000-0xd3fff has been reserved
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0xf0000-0xf7fff could not be reserved
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0xf8000-0xfbfff could not be reserved
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0xfc000-0xfffff could not be reserved
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0xfff0000-0xfffffff could not be reserved
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0xffff0000-0xffffffff has been reserved
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0x0-0x9ffff could not be reserved
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0x100000-0xffeffff could not be reserved
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0xfec00000-0xfec00fff could not be reserved
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0xfee00000-0xfee00fff has been reserved
Dec 10 18:11:27 Tower kernel: system 00:00: iomem range 0xfff80000-0xfffeffff has been reserved
Dec 10 18:11:27 Tower kernel: system 00:02: ioport range 0x4d0-0x4d1 has been reserved
Dec 10 18:11:27 Tower kernel: system 00:02: ioport range 0x800-0x805 has been reserved
Dec 10 18:11:27 Tower kernel: pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
Dec 10 18:11:27 Tower kernel: pci 0000:00:01.0:   IO window: disabled
Dec 10 18:11:27 Tower kernel: pci 0000:00:01.0:   MEM window: 0xda000000-0xdbffffff
Dec 10 18:11:27 Tower kernel: pci 0000:00:01.0:   PREFETCH window: 0xd8000000-0xd9ffffff
Dec 10 18:11:27 Tower kernel: pci 0000:00:01.0: setting latency timer to 64
Dec 10 18:11:27 Tower kernel: pci_bus 0000:00: resource 0 io:  [0x00-0xffff]
Dec 10 18:11:27 Tower kernel: pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff]
Dec 10 18:11:27 Tower kernel: pci_bus 0000:01: resource 1 mem: [0xda000000-0xdbffffff]
Dec 10 18:11:27 Tower kernel: pci_bus 0000:01: resource 2 pref mem [0xd8000000-0xd9ffffff]
Dec 10 18:11:27 Tower kernel: NET: Registered protocol family 2
Dec 10 18:11:27 Tower kernel: IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
Dec 10 18:11:27 Tower kernel: TCP established hash table entries: 8192 (order: 4, 65536 bytes)
Dec 10 18:11:27 Tower kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Dec 10 18:11:27 Tower kernel: TCP: Hash tables configured (established 8192 bind 8192)
Dec 10 18:11:27 Tower kernel: TCP reno registered
Dec 10 18:11:27 Tower kernel: NET: Registered protocol family 1
Dec 10 18:11:27 Tower kernel: Unpacking initramfs...
Dec 10 18:11:27 Tower kernel: Freeing initrd memory: 51650k freed
Dec 10 18:11:27 Tower kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Dec 10 18:11:27 Tower kernel: fuse init (API version 7.12)
Dec 10 18:11:27 Tower kernel: io scheduler noop registered (default)
Dec 10 18:11:27 Tower kernel: io scheduler anticipatory registered
Dec 10 18:11:27 Tower kernel: io scheduler deadline registered
Dec 10 18:11:27 Tower kernel: io scheduler cfq registered
Dec 10 18:11:27 Tower kernel: pci 0000:00:01.0: disabling DAC on VIA PCI bridge
Dec 10 18:11:27 Tower kernel: pci 0000:01:00.0: Boot video device
Dec 10 18:11:27 Tower kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
Dec 10 18:11:27 Tower kernel: ACPI: Power Button [PWRF]
Dec 10 18:11:27 Tower kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
Dec 10 18:11:27 Tower kernel: ACPI: Power Button [PWRB]
Dec 10 18:11:27 Tower kernel: input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2
Dec 10 18:11:27 Tower kernel: ACPI: Sleep Button [sLPB]
Dec 10 18:11:27 Tower kernel: fan PNP0C0B:00: registered as cooling_device0
Dec 10 18:11:27 Tower kernel: ACPI: Fan [FAN] (on)
Dec 10 18:11:27 Tower kernel: Marking TSC unstable due to TSC halts in idle
Dec 10 18:11:27 Tower kernel: ACPI: CPU0 (power states: C1[C1] C2[C2])
Dec 10 18:11:27 Tower kernel: processor LNXCPU:00: registered as cooling_device1
Dec 10 18:11:27 Tower kernel: ACPI: Processor [CPU0] (supports 2 throttling states)
Dec 10 18:11:27 Tower kernel: thermal LNXTHERM:01: registered as thermal_zone0
Dec 10 18:11:27 Tower kernel: ACPI: Thermal Zone [THRM] (39 C)
Dec 10 18:11:27 Tower kernel: lp: driver loaded but no devices found
Dec 10 18:11:27 Tower kernel: Real Time Clock Driver v1.12b
Dec 10 18:11:27 Tower kernel: Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Dec 10 18:11:27 Tower kernel: Hangcheck: Using get_cycles().
Dec 10 18:11:27 Tower kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
Dec 10 18:11:27 Tower kernel: Floppy drive(s): fd0 is 1.44M
Dec 10 18:11:27 Tower kernel: FDC 0 is a post-1991 82077
Dec 10 18:11:27 Tower kernel: loop: module loaded
Dec 10 18:11:27 Tower kernel: Uniform Multi-Platform E-IDE driver
Dec 10 18:11:27 Tower kernel: e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
Dec 10 18:11:27 Tower kernel: e100: Copyright(c) 1999-2006 Intel Corporation
Dec 10 18:11:27 Tower kernel: Broadcom NetXtreme II CNIC Driver cnic v2.0.0 (May 21, 2009)
Dec 10 18:11:27 Tower kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [ALKB] BIOS reported IRQ 0, using IRQ 21
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 21
Dec 10 18:11:27 Tower kernel: ehci_hcd 0000:00:10.3: PCI INT D -> Link[ALKB] -> GSI 21 (level, low) -> IRQ 21
Dec 10 18:11:27 Tower kernel: ehci_hcd 0000:00:10.3: EHCI Host Controller
Dec 10 18:11:27 Tower kernel: ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
Dec 10 18:11:27 Tower kernel: ehci_hcd 0000:00:10.3: irq 21, io mem 0xdc024000
Dec 10 18:11:27 Tower kernel: ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00
Dec 10 18:11:27 Tower kernel: usb usb1: configuration #1 chosen from 1 choice
Dec 10 18:11:27 Tower kernel: hub 1-0:1.0: USB hub found
Dec 10 18:11:27 Tower kernel: hub 1-0:1.0: 6 ports detected
Dec 10 18:11:27 Tower kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Dec 10 18:11:27 Tower kernel: uhci_hcd: USB Universal Host Controller Interface driver
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.0: PCI INT A -> Link[ALKB] -> GSI 21 (level, low) -> IRQ 21
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.0: UHCI Host Controller
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.0: irq 21, io base 0x0000d400
Dec 10 18:11:27 Tower kernel: usb usb2: configuration #1 chosen from 1 choice
Dec 10 18:11:27 Tower kernel: hub 2-0:1.0: USB hub found
Dec 10 18:11:27 Tower kernel: hub 2-0:1.0: 2 ports detected
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.1: PCI INT B -> Link[ALKB] -> GSI 21 (level, low) -> IRQ 21
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.1: UHCI Host Controller
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.1: irq 21, io base 0x0000d800
Dec 10 18:11:27 Tower kernel: usb usb3: configuration #1 chosen from 1 choice
Dec 10 18:11:27 Tower kernel: hub 3-0:1.0: USB hub found
Dec 10 18:11:27 Tower kernel: hub 3-0:1.0: 2 ports detected
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.2: PCI INT C -> Link[ALKB] -> GSI 21 (level, low) -> IRQ 21
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.2: UHCI Host Controller
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
Dec 10 18:11:27 Tower kernel: uhci_hcd 0000:00:10.2: irq 21, io base 0x0000dc00
Dec 10 18:11:27 Tower kernel: usb usb4: configuration #1 chosen from 1 choice
Dec 10 18:11:27 Tower kernel: hub 4-0:1.0: USB hub found
Dec 10 18:11:27 Tower kernel: hub 4-0:1.0: 2 ports detected
Dec 10 18:11:27 Tower kernel: Initializing USB Mass Storage driver...
Dec 10 18:11:27 Tower kernel: usbcore: registered new interface driver usb-storage
Dec 10 18:11:27 Tower kernel: USB Mass Storage support registered.
Dec 10 18:11:27 Tower kernel: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
Dec 10 18:11:27 Tower kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Dec 10 18:11:27 Tower kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Dec 10 18:11:27 Tower kernel: mice: PS/2 mouse device common for all mice
Dec 10 18:11:27 Tower kernel: input: PC Speaker as /devices/platform/pcspkr/input/input3
Dec 10 18:11:27 Tower kernel: it87: Found IT8705F chip at 0x290, revision 2
Dec 10 18:11:27 Tower kernel: ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region IP__ [0x295-0x296]
Dec 10 18:11:27 Tower kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Dec 10 18:11:27 Tower kernel: cpuidle: using governor ladder
Dec 10 18:11:27 Tower kernel: usbcore: registered new interface driver hiddev
Dec 10 18:11:27 Tower kernel: usbcore: registered new interface driver usbhid
Dec 10 18:11:27 Tower kernel: usbhid: v2.6:USB HID core driver
Dec 10 18:11:27 Tower kernel: TCP cubic registered
Dec 10 18:11:27 Tower kernel: NET: Registered protocol family 17
Dec 10 18:11:27 Tower kernel: RPC: Registered udp transport module.
Dec 10 18:11:27 Tower kernel: RPC: Registered tcp transport module.
Dec 10 18:11:27 Tower kernel: Using IPI No-Shortcut mode
Dec 10 18:11:27 Tower kernel: Freeing unused kernel memory: 292k freed
Dec 10 18:11:27 Tower kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
Dec 10 18:11:27 Tower kernel: skge 0000:00:0c.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Dec 10 18:11:27 Tower kernel: skge 0000:00:0c.0: PCI: Disallowing DAC for device
Dec 10 18:11:27 Tower kernel: skge 1.13 addr 0xdc020000 irq 19 chip Yukon rev 1
Dec 10 18:11:27 Tower kernel: skge eth0: addr 00:13:46:99:37:a0
Dec 10 18:11:27 Tower kernel: via82cxxx 0000:00:11.1: VIA vt8235 (rev 00) IDE UDMA133
Dec 10 18:11:27 Tower kernel: via82cxxx 0000:00:11.1: IDE controller (0x1106:0x0571 rev 0x06)
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [ALKA] BIOS reported IRQ 0, using IRQ 20
Dec 10 18:11:27 Tower kernel: ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
Dec 10 18:11:27 Tower kernel: VIA_IDE 0000:00:11.1: PCI INT A -> Link[ALKA] -> GSI 20 (level, low) -> IRQ 20
Dec 10 18:11:27 Tower kernel: via82cxxx 0000:00:11.1: not 100%% native mode: will probe irqs later
Dec 10 18:11:27 Tower kernel:     ide0: BM-DMA at 0xe000-0xe007
Dec 10 18:11:27 Tower kernel:     ide1: BM-DMA at 0xe008-0xe00f
Dec 10 18:11:27 Tower kernel: Probing IDE interface ide0...
Dec 10 18:11:27 Tower kernel: hda: FUJITSU MPA3035ATU, ATA DISK drive
Dec 10 18:11:27 Tower kernel: hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
Dec 10 18:11:27 Tower kernel: hda: UDMA/33 mode selected
Dec 10 18:11:27 Tower kernel: Probing IDE interface ide1...
Dec 10 18:11:27 Tower kernel: hdc: ST320413A, ATA DISK drive
Dec 10 18:11:27 Tower kernel: hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
Dec 10 18:11:27 Tower kernel: hdc: UDMA/100 mode selected
Dec 10 18:11:27 Tower kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Dec 10 18:11:27 Tower kernel: ide1 at 0x170-0x177,0x376 on irq 15
Dec 10 18:11:27 Tower kernel: ide-gd driver 1.18
Dec 10 18:11:27 Tower kernel: hda: max request size: 128KiB
Dec 10 18:11:27 Tower kernel: hda: 6835952 sectors (3500 MB), CHS=6781/16/63
Dec 10 18:11:27 Tower kernel:  hda: hda1
Dec 10 18:11:27 Tower kernel: hdc: max request size: 128KiB
Dec 10 18:11:27 Tower kernel: hdc: 39102336 sectors (20020 MB) w/1024KiB Cache, CHS=38792/16/63
Dec 10 18:11:27 Tower kernel: hdc: cache flushes not supported
Dec 10 18:11:27 Tower kernel:  hdc: hdc1
Dec 10 18:11:27 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig lo 127.0.0.1
Dec 10 18:11:27 Tower logger: /etc/rc.d/rc.inet1:  /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
Dec 10 18:11:27 Tower ifplugd(eth0)[933]: ifplugd 0.28 initializing.
Dec 10 18:11:27 Tower ifplugd(eth0)[933]: Using interface eth0/00:13:46:99:37:A0 with driver <skge> (version: 1.13)
Dec 10 18:11:27 Tower ifplugd(eth0)[933]: Using detection mode: SIOCETHTOOL
Dec 10 18:11:27 Tower ifplugd(eth0)[933]: Initialization complete, link beat not detected.
Dec 10 18:11:27 Tower kernel: skge eth0: enabling interface
Dec 10 18:11:27 Tower rpc.statd[945]: Version 1.1.4 Starting
Dec 10 18:11:27 Tower emhttp: unRAID System Management Utility version 4.5-beta13
Dec 10 18:11:27 Tower emhttp: Copyright (C) 2005-2009, Lime Technology, LLC
Dec 10 18:11:27 Tower emhttp: find_flash_dir: no sd
Dec 10 18:11:27 Tower emhttp: check_registration: no flash device
Dec 10 18:11:27 Tower emhttp: Unregistered
Dec 10 18:11:27 Tower emhttp: Device inventory:
Dec 10 18:11:27 Tower emhttp: pci-0000:00:11.1-ide-0:0 ide0 (hda) ata-FUJITSU_MPA3035ATU_01252830
Dec 10 18:11:27 Tower emhttp: pci-0000:00:11.1-ide-1:0 ide1 (hdc) ata-ST320413A_5ED3DPHG
Dec 10 18:11:27 Tower emhttp: find_flash_dir: no sd
Dec 10 18:11:27 Tower emhttp: check_registration: no flash device
Dec 10 18:11:27 Tower emhttp: shcmd (1): rmmod md-mod >>/var/log/go 2>&1
Dec 10 18:11:27 Tower emhttp: _shcmd: shcmd (1): exit status: 1
Dec 10 18:11:27 Tower emhttp: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=0,0,22,0,0,0 >>/var/log/go 2>&1
Dec 10 18:11:27 Tower kernel: xor: automatically using best checksumming function: pIII_sse
Dec 10 18:11:27 Tower kernel:    pIII_sse  :  3894.000 MB/sec
Dec 10 18:11:27 Tower kernel: xor: using function: pIII_sse (3894.000 MB/sec)
Dec 10 18:11:27 Tower kernel: md: unRAID driver 0.95.3 installed
Dec 10 18:11:27 Tower emhttp: Spinning up all drives...
Dec 10 18:11:27 Tower kernel: md: disk0 removed
Dec 10 18:11:27 Tower kernel: md: import disk1: [22,0] (hdc) ST320413A 5ED3DPHG offset: 63 size: 19551136
Dec 10 18:11:27 Tower kernel: mdcmd (2): set md_num_stripes 1280
Dec 10 18:11:27 Tower kernel: mdcmd (3): set md_write_limit 768
Dec 10 18:11:27 Tower kernel: mdcmd (4): set md_sync_window 288
Dec 10 18:11:27 Tower kernel: mdcmd (5): set spinup_group 1 0
Dec 10 18:11:27 Tower kernel: mdcmd (6): spinup 1
Dec 10 18:11:27 Tower emhttp: shcmd (3): /usr/local/sbin/set_ncq hdc 1 >/dev/null
Dec 10 18:11:27 Tower kernel: mdcmd (: start STOPPED
Dec 10 18:11:27 Tower kernel: unraid: allocating 13100K for 1280 stripes (2 disks)
Dec 10 18:11:27 Tower kernel: md1: running, size: 19551136 blocks
Dec 10 18:11:27 Tower emhttp: shcmd (4): mkdir /mnt/disk1
Dec 10 18:11:27 Tower kernel: mdcmd (10): check 
Dec 10 18:11:27 Tower emhttp: shcmd (5): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1  >/dev/null 2>&1
Dec 10 18:11:27 Tower kernel: md: recovery thread woken up ...
Dec 10 18:11:27 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal
Dec 10 18:11:27 Tower kernel: REISERFS (device md1): using ordered data mode
Dec 10 18:11:27 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Dec 10 18:11:27 Tower kernel: REISERFS (device md1): checking transaction log (md1)
Dec 10 18:11:28 Tower kernel: REISERFS (device md1): Using r5 hash to sort names
Dec 10 18:11:28 Tower kernel: md: recovery thread has nothing to resync
Dec 10 18:11:28 Tower emhttp: shcmd (6): rm /etc/samba/smb-shares.conf >/dev/null 2>&1
Dec 10 18:11:28 Tower emhttp: _shcmd: shcmd (6): exit status: 1
Dec 10 18:11:28 Tower emhttp: shcmd (7): cp /etc/exports- /etc/exports
Dec 10 18:11:28 Tower emhttp: shcmd (: killall -HUP smbd
Dec 10 18:11:28 Tower emhttp: shcmd (9): /etc/rc.d/rc.nfsd restart | logger
Dec 10 18:11:29 Tower kernel: skge eth0: Link is up at 1000 Mbps, full duplex, flow control both
Dec 10 18:11:30 Tower ifplugd(eth0)[933]: Link beat detected.
Dec 10 18:11:31 Tower ifplugd(eth0)[933]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Dec 10 18:11:31 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 hw ether 00:24:01:14:F0:C2
Dec 10 18:11:31 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 192.168.0.72 broadcast 192.168.0.255 netmask 255.255.255.0
Dec 10 18:11:31 Tower logger: /etc/rc.d/rc.inet1:  /sbin/route add default gw 192.168.0.1 metric 1
Dec 10 18:11:31 Tower ifplugd(eth0)[933]: Program executed successfully.
Dec 10 18:20:38 Tower login[9280]: ROOT LOGIN  on `tty1'

 

Anyone any ideas?

Share this post


Link to post

OK, I've just upgraded to UnRaid 4.5Final, as well as installed boof's updated rtorrent packages and places these in /boot/packages/rtorrent.

 

Same message happening in rutorrent.

 

Remember, I am a complete noob to linux commands, but have been getting around the unraid system.  Unraid box is connected via KVM, and I can happily connect via telnet as well (makes it easier to copy/paste commands).

 

Iv'e also changed my gigabit nic, as this was not always activating, causing no IP address, new nic, working every boot (so far :-X).

 

I had it working once, downloaded a torrent from torrential.ws, and started it going, to see if private trackers were working, didn't complete the download, as needed to power off.

 

Tried 'screen -ls', came back with:

No Sockets found in /root/.screen.

 

Any ideas? please? :'(

Share this post


Link to post

Hi Phoenix, it seems that screen did not start. Telnet into unraid and type the following:

 

screen (press enter)
/usr/bin/rtorrent -n -o import=/boot/custom/etc/rtorrent.rc

 

This should start rtorrent in a screen session manually, and rutorrent should work fine at this point. If it does, something is wrong with your go script. post it here so I can have a look at it. If there is an error post the error and we'll see what might be causing rtorrent from starting.

Share this post


Link to post

Hi Flixxx

 

OK, followed your instructions

Telnet into box and typed

'screen' pressed enter

 

got come text on screen, last line saying press a key

pasted '/usr/bin/rtorrent -n -o import=/boot/custom/etc/rtorrent.rc'

 

got this back

root@Tower:~# /usr/bin/rtorrent -n -o import=/boot/custom/etc/rtorrent.rc
rtorrent: Failed to parse command line option: Error in option file: /boot/custo
m/etc/rtorrent.rc:16: Invalid start of name.

 

my 'go' file

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
#We will now install Unraid-Web
installpkg /boot/packages/unraidweb/*
#Install Screen
mkdir /var/log/wtmp
installpkg /boot/packages/screen/*
#Install rtorrent
installpkg /boot/packages/rtorrent/*
#Removing locked rtorrent from session in case of bad reboot
rm /mnt/disk1/torrents/downloading/rtorrent.session/rtorrent.lock
#Starting rtorrent
/usr/bin/screen -dmS rtorrent /usr/bin/rtorrent -n -o import=/boot/custom/etc/rtorrent.rc
#Create symbolic link for .screen
ln -s /.screen /root/

 

I also upped my ram to 768MB as was running only 256.

 

I looked in /usr folder, I could not see a 'rtorrent' file in this folder.

 

 

Share this post


Link to post

According to the error, something is wrong with your rtorrent.rc file. Download notepad++ (It's a free download, you can google it) and edit your rtorrent.rc file in there and save it. Sometimes windows notepad messes up the file (For example you might see a lot of ^M). If it still fails, make a new rtorrent.rc file and keep it simple, below is an example you can use, just change the default directory to one that you want (Make sure it exists on your drive or it may give you an error again).

 

# Global upload and download rate in KiB. "0" for unlimited.
download_rate = 600
upload_rate = 40

# Default directory to save the downloaded torrents.
directory = /mnt/user/downloads

# Port range to use for listening.
port_range = 2335-2335

scgi_port = 127.0.0.1:5000

Share this post


Link to post

Thanks, will do that tonight.  BTW, I used wordpad for editing, as someone else mentioned that notepad doesn't do unix codes correctly??  Anyway got notepad++ to install at home so will copy your sample as a test.

 

I did get a sample rtorrent.rc file from rakshasa site, but haven't done anything with that yet.  Let you know what I find.

 

Cheers

Share this post


Link to post

OK, I have got it working after every boot/reboot.  It seemed that rtorrent didn't want to start.

I tried 'pidof rtorrent' in telnet, with no data back.

 

I loaded up the rc.rtorrent script from henris: http://lime-technology.com/forum/index.php?topic=4029.msg44645#msg44645. and modified it to start the relevant files for my configuration.

 

When I set the command rc.rtorrent start, all seemed ok, but doing a rc.rtorrent status, said rtorrent not started.

 

Confusion :o

 

SO I decided to start from the beginning.  Disconnected my HD and found it formatted as 'FATt32', so set a 1.2G partition and formatted to 'FAT'. named it 'UNRAID' and ran 'syslinux -maf j:'

Copied over the UNRAID 4.5FINAL files and reconnected to my box.

 

Booted up and changed my network settings.

 

Copied over all the packages, created folders '/custom', '/custom/etc', '/custom/lighttpd' and '/config/lighttpd'

 

As I had the packages folder already with rtorrent, screen and unraidweb, I followed your instructions for additions to the 'go' file for package installations.

 

I already had the files for rutorrent extracted to '/mnt/disk1/wwwdocs' so no need to repeat.

 

I put a new rtorrent.rc file from your last post in '/custom/etc'.

 

Copied '/config/lighttpd/lighttpd.conf.include' to /custom/lighttpd' folder and rebooted.

 

Held my breath, and tried //tower:86 in firefox.  All good so far.

 

So stop torrent downloading and rebooted the box.  Tried web access again, and all going perfectly.

 

I can not say what was causing the problem.  I suspect the rtorrent.rc file, but I had tried your settings as well with no joy.  I do believe starting again may have blown out the bugs (my stuff-ups) and got things working again.

 

PS, just tried 'pidof rtorrent' with answer 9278.  It's sure working now.

 

 

Many Thanks to Flixxx for the tutorial and advice.   ;D

Share this post


Link to post

OK, I have got it working after every boot/reboot.  It seemed that rtorrent didn't want to start.

I tried 'pidof rtorrent' in telnet, with no data back.

 

I loaded up the rc.rtorrent script from henris: http://lime-technology.com/forum/index.php?topic=4029.msg44645#msg44645. and modified it to start the relevant files for my configuration.

 

When I set the command rc.rtorrent start, all seemed ok, but doing a rc.rtorrent status, said rtorrent not started.

 

Confusion :o

I actually noticed same kind of behaviour when coding the rc.rtorrent. I had a copy-paste error in the filename for the rtorrent config and the rtorrent just would not start. To my recollection there was no error reported and when launching through a detached screen any error messages would of course be lost anyhow. I will add a check to "rc.rtorrent start" to verify that the rtorrent was truely started. I will also add a check that the config file to be used really exists. They should have been there from the start but they just slipped my mind during the late hours... I will post an updated version later this evening (23.00 GMT+2, Finnish time  ;))

 

Btw, you can easily use the mentioned rc.rtorrent side-by-side with otherwise fully working rtorrent+screen+rutorrent installation. The only dependency I can think of is the rc.rtorrent activate which attaches to a screen named "rtorrentd" which is different from the Flixx's instructions' screen name "rtorrent". Start/stop/restart/status will work regardless of who originally started or stopped the rtorrent. If you take a look inside rc.rtorrent you will find pretty much the same code as Flixx's (partially direct copy-paste ;D) with some additional things I found out to be usefull like disabling "stty START/STOP" (regards to Weebotech) which are used by rtorrent gui (ctrl-q for exit).

Share this post


Link to post
I leave it up to you to configure the rtorrent.rc file the way you want it.

Flixxx. I was working through the instructions and got stuck with this. Where is this rtorrent.rc file (I do get cross-eyed in the wee-hours)?

 

 

Share this post


Link to post

You have to create one. You can either go to rtorrent main website to get a sample, or there might be a few floating around here.

Share this post


Link to post

Darn it!  I'm still having problems.  after two - three hours it just stops. 

 

Please, are there any logs I can get that will tell me what's going on, or not going on.

 

I tried to add to the rtorrent.rc file

execute_log = /var/log/rtorrent.log

 

This  was to get a log if there was a problem, but with it in the rtorrent.rc file, it stops rtorrent from kicking into gear at all.

 

Any thought would be appreciated.

 

Share this post


Link to post

Darn it!  I'm still having problems.  after two - three hours it just stops. 

 

Please, are there any logs I can get that will tell me what's going on, or not going on.

 

I tried to add to the rtorrent.rc file

execute_log = /var/log/rtorrent.log

 

This  was to get a log if there was a problem, but with it in the rtorrent.rc file, it stops rtorrent from kicking into gear at all.

 

Any thought would be appreciated.

 

I couldn´t find anything on rtorrent log file. It seems there is no general one, the execute_log seems to be related only to executed commands (I assume this means the commands automatically executed by rtorrent based on the config, like stopping and removing torrents once finished).

 

For me enabling the execute_log works (I copy pasted the exact code from your post), rtorrent starts up and rtorrent.log appears in /var/log. However there were no entries thus far so it might not help you. I have posted my rtorrent.rc config file in the rtorrent thread, you could take a look:

http://lime-technology.com/forum/index.php?topic=4029.msg44645#msg44645

Share this post


Link to post

Darn it!  I'm still having problems.  after two - three hours it just stops. 

 

Please, are there any logs I can get that will tell me what's going on, or not going on.

 

I tried to add to the rtorrent.rc file

execute_log = /var/log/rtorrent.log

 

This  was to get a log if there was a problem, but with it in the rtorrent.rc file, it stops rtorrent from kicking into gear at all.

 

Any thought would be appreciated.

 

I couldn´t find anything on rtorrent log file. It seems there is no general one, the execute_log seems to be related only to executed commands (I assume this means the commands automatically executed by rtorrent based on the config, like stopping and removing torrents once finished).

 

For me enabling the execute_log works (I copy pasted the exact code from your post), rtorrent starts up and rtorrent.log appears in /var/log. However there were no entries thus far so it might not help you. I have posted my rtorrent.rc config file in the rtorrent thread, you could take a look:

http://lime-technology.com/forum/index.php?topic=4029.msg44645#msg44645

 

Cheers henris

 

Unfortunately,  I'll have to wait till the weekend as we've got carpet going down in the next two days, so I'm running skeletal computer system.

 

I'll try your rtorrent.rc file, but I was having some strange behaviour also, with the whole system locking up.  couldn't telnet in, nor use the kvm to see what was going on.  I figure I have to run a memtest overnight to see if I have a ram issue.  damn it. thought it was all go.

 

Anyone know of any logs to check for errors relating to system crash or lock ups.  I had a trace message on screen once, but couldn't make out what it was about.

 

Thanks henris,  will keep you informed as to my progress.

 

Cheers, Rob

 

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.