PDA

View Full Version : getting the bugs out of the system


tsella
October 30th, 2008, 01:20 PM
with the (extreme) popularity of boxee on apple tv, the number of reports on infamous error 6, 10, 11 have increased as well.

WE NEED YOU

we want to fix these errors, but for that we really need your assistance in the form of sending us your logs, and following our guidance as necessary.

for your convinience we've created a new mailbox for this purpose

allyourbugs@boxee.tv

whenever your boxee on atv goes into an error, please do the following:

from Mac and Linux


open terminal
execute the following commands:
scp frontrow@{apple tv ip}:/Library/Logs/Console/501/console.log .
scp frontrow@{apple tv ip}:/Users/frontrow/Library/Logs/CrashReporter/CrashReporter.log .
scp frontrow@{apple tv ip}:/Users/frontrow/Library/Logs/boxee.log .
scp frontrow@{apple tv ip}:/Users/frontrow/Library/Logs/boxee.old.log .
tar cvzf {boxee user}_atv.tgz console.log CrashReporter.log boxee.log boxee.old.log
email us the resultant {boxee user}_atv.tgz file to allyourbugs@boxee.tv noting what you were doing prior to the crash with as much details as possible. we will get back to you, possibly asking to try a couple of things.


from Windows


get putty and install: http://the.earth.li/~sgtatham/putty/latest/x86/putty-0.60-installer.exe
open a command line by using Windows Key+R and typing cmd
at command line, execute the following:

cd "c:\Program Files\PuTTY"
pscp frontrow@{apple tv ip}:/Library/Logs/Console/501/console.log .
pscp frontrow@{apple tv ip}:/Users/frontrow/Library/Logs/CrashReporter/CrashReporter.log .
pscp frontrow@{apple tv ip}:/Users/frontrow/Library/Logs/boxee.log .
pscp frontrow@{apple tv ip}:/Users/frontrow/Library/Logs/boxee.old.log .

from My Computer, go to C: > Program Files > PuTTY
select console.log CrashReporter.log boxee.log boxee.old.log (to multiple select files, mouse left click on each file while holding CTRL on the keyboard)
mouse right click > Send To > Compressed (zipped) Folder
rename the resultant zip file as {boxee user}_atv.zip
email us the resultant {boxee user}_atv.zip file to allyourbugs@boxee.tv noting what you were doing prior to the crash with as much details as possible. we will get back to you, possibly asking to try a couple of things.


note: the above scp/pscp commands use a protocol that at first time will ask you to accept digital signatures, and will follow by asking for a password. accept the signature, and the password is frontrow.

every reported error X which results in code change on our part, will get you some boxee goodies!
more than one? you're on a distinguished road to get your name into boxee's credits screen!

universaldilettant
November 1st, 2008, 08:13 AM
Unfortunately the log files created by boxe contain your full login credentials for Network shares. Don't post them without ridding the passwords.

This is a real security problem as people tend to use same passwords for lots of things and sometimes NAS devices can be reached from the internet as well.


steffen

giovanisp
November 3rd, 2008, 08:55 AM
well, first fix should be replacing our full login credentials on logs with ****** :-)

agentlame
November 3rd, 2008, 09:11 AM
well, first fix should be replacing our full login credentials on logs with ****** :-)

anyone with physical access to you computer, probably won't need you password. ;)

imksn
November 3rd, 2008, 02:20 PM
The problem I think universaldilettant brings up is that oftentimes one uses the same username and password for all over the web.

daveo78
November 4th, 2008, 08:26 PM
Heres the instructions in script form (for MAC/Linux users) to make your life easier. Open up terminal.app make a directory in you home folder mkdir boxeelogs create a blank file and name it whatever you wanttouch getboxeelogs.sh make it executable, chmod 700 getboxeelogs.sh open the file for writingnano getboxeelogs.sh copy the following text into it and fill in values with your info
#!/bin/sh
ATV= #Put ATV IP here
USER=frontrow #ATV user, most likely its frontrow
BOXEEUSER= #Your Boxee username

scp $USER@$ATV:/Library/Logs/Console/501/console.log .
scp $USER@$ATV:/Users/frontrow/Library/Logs/CrashReporter/CrashReporter.log .
scp $USER@$ATV:/Users/frontrow/Library/Logs/boxee.log .
scp $USER@$ATV:/Users/frontrow/Library/Logs/boxee.old.log .
tar cvzf $BOXEEUSER_atv.tgz console.log CrashReporter.log boxee.log boxee.old.log
and run it from there../getboxeelogs.sh It dosent strip out the passwords and such but it'll get everything in one place. If you need to remove passwords from the file you should comment out the last line so it wont tar the files#tar cvzf $BOXEEUSER_atv.tgz console.log CrashReporter.log boxee.log boxee.old.logand then run the tar command manually after.

If you guys could tell me what format the line is in with usernames and passwords ill make the script strip them out automatically. I use NFS shares so my logs don't contain any password info for me to clean. And yes I agree with giovannisp the passwords should be blanked out in the log files from the start.

universaldilettant
November 5th, 2008, 06:00 AM
the lines containing the login credentials are as follows.

11:54:47 T:52166656 M: 4190208 WARNING: CMetadataResolverVideo::GetMovieDetails, RESOLVER, no entries for key (season = 2, episode = 21) [path=smb://USERNAME:PASSWORD@IP-NUMBER/linkstation/TV Shows/Carnivale/Season 2/Carnivale - S02E21 - Lincoln Highway.avi]

again. passwords and so on should NEVER be saved in cleartext. especially not in log files.

I don't know why I even have to mention that.

not everyone has just one computer at home. my network is accescible by a couple of persons. also appletv username and password is frontrow:frontrow so everybody has access to that logfiles which means everybody has access to your passwords etc. just by having access to your network. this is a blatant security flaw.

boxee, you guys want a lot of information from your users, i mean what music i hear, what films i watch etc. you better make sure that this information is secured. otherwise you have a serious problem. if i can't trust you i can't use your software.

tsella
November 6th, 2008, 09:14 AM
for every file you could do something like (on your mac or atv):


sed -i '' "s/:\/\/.*:.*@/:\/\/XXX:XXX@/g" {filename}


for example:

sed -i '' "s/:\/\/.*:.*@/:\/\/XXX:XXX@/g" /Users/frontrow/Library/Logs/boxee.log


will remove all username/password from boxee.log

and @universaldilettant, we are aware of this and have a bug open in this regards.

tsella
November 6th, 2008, 09:39 AM
@daveo78 thanks for the script idea, here is my take on it:


#!/bin/sh

ATV= # YOUR ATV IP ADDRESS
USER=frontrow
BOXEEUSER= # YOUR BOXEE USERNAME

NOW=`date "+%Y%m%d%H%M"`
FILES="/Library/Logs/Console/501/console.log /Users/${USER}/Library/Logs/boxee.* /Users/${USER}/Library/Logs/CrashReporter/CrashReporter.log"

mkdir .bx${NOW}

for f in ${FILES}
do
LOCALNAME=".bx${NOW}/`basename ${f}`"
scp ${USER}@${ATV}:${f} ${LOCALNAME}
sed -i '' "s/:\/\/.*:.*@/:\/\/XXX:XXX@/g" ${LOCALNAME}
done
tar cvzf boxee_${NOW}_${BOXEEUSER}.tgz .bx${NOW}/*
rm -rf .bx${NOW}

daveo78
November 7th, 2008, 08:50 PM
Cool, much better than mine.

giyad
November 12th, 2008, 01:59 PM
I see you've included "sed -i '' "s/:\/\/.*:.*@/:\/\/XXX:XXX@/g" ${LOCALNAME}". does that mean it will remove the username/passwords from boxee.log?

Do i need to adjust anything other than the first two comments?

What do I do once I've copied the code into getboxeelogs.sh? Do I close the window?

Sorry, im not too savvy with scripts...

tsella
November 13th, 2008, 10:34 AM
you need to set the atv ip for ATV= and your boxee user for BOXEEUSER=

yes, this script will cleanup your username/password

after saving the script, run it from terminal using sh ./getboxeelogs.sh

dirtysteve
November 13th, 2008, 11:54 AM
Adding boxee is the only change I've made on my ATV. If someone could tell me how to access terminal, and send the user log I would be happy to provide feedback on issues I encounter.

So far, I've only encountered two problems... (error 11, and the inability to exit XMBC-> maybe a window size / setting issue?) and I've been using boxee quite a bit.

I love this addition to my ATV. Thank you for all of your work!

imksn
November 13th, 2008, 12:08 PM
Adding boxee is the only change I've made on my ATV. If someone could tell me how to access terminal, and send the user log I would be happy to provide feedback on issues I encounter.

If you are running Mac OS 10.5, "apple key" + "space bar" > type "terminal" > check to make sure "terminal" is highlighted in the spotlight dropdown upper right and click "enter"

Follow directions for getting log files and where to send here:

http://forum.boxee.tv/showthread.php?p=7800#post7800

giyad
November 14th, 2008, 06:06 PM
I sent in a log file, please let me know if it worked, I couldn't get the tgz to unarchive myself... maybe the script didn't work

jmelloy
November 16th, 2008, 02:08 PM
I tried your script, and the shell glob didn't work to grab both boxee logs.

Also, if you are on a macor have Bonjour installed, you can usually use AppleTV.local.


#!/bin/sh

ATV=AppleTV.local # YOUR ATV IP ADDRESS
USER=frontrow
BOXEEUSER= # YOUR BOXEE USERNAME

NOW=`date "+%Y%m%d%H%M"`
FILES="/Library/Logs/Console/501/console.log /Users/${USER}/Library/Logs/boxee.log /Users/${USER}/Library/Logs/boxee.old.log /Users/${USER}/Library/Logs/CrashReporter/CrashReporter.log"

mkdir .bx${NOW}

for f in ${FILES}
do
LOCALNAME=".bx${NOW}/`basename ${f}`"
scp ${USER}@${ATV}:${f} ${LOCALNAME}
sed -i '' "s/:\/\/.*:.*@/:\/\/XXX:XXX@/g" ${LOCALNAME}
done
tar cvzf boxee_${NOW}_${BOXEEUSER}.tgz .bx${NOW}/*
rm -rf .bx${NOW}

janngobble
November 20th, 2008, 07:19 PM
I tried your script, and the shell glob didn't work to grab both boxee logs.

Also, if you are on a macor have Bonjour installed, you can usually use AppleTV.local.



Bonjour only works if you have only 1 AppleTV. Would be better if the Bonjour name was sensed on the network and a digit added to the end, like AppleTV1, AppleTV2, etc :) But that is hoping ...

I had to go to each ATV and get the IPs for all 3 of them.

:)

pkeenan
November 20th, 2008, 08:16 PM
Gentlemen, A bit confused since I am but a humble "end-user" without much programming experience, OK, no programming experience. Using much effort I was able to figure out a FUGU access to my Apple TV and I can see the logs you're speaking of but I can't seem to find the area within the logs I should be protecting myself from that would give you information other then what you're looking for. Is there a way in CONSOLE to "filter" the area to change? I used the words "password" and "User". There doesn't seem to be any info on me other than what deals directly with Boxee.

Let me know. Happy to pass on the goods. By the way. Upgraded Boxee after having had it run successfully prior to the upgrade. Got a error 10 and that's why I'm here. Apple TV is still in 2.2 mode.

Thanks,

Peter

giyad
November 21st, 2008, 11:34 AM
Does Boxee need to be open to get the logs, or should it be closed, or does it not matter? I am having trouble getting the logs to work. I've done everything you say, and it creates a .tgz file for me, but nothing is in the tar when I open it. This is what I get:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
8e:ea:1e:de:d6:7d:2c:29:74:cb:0f:aa:e2:55:0e:06.
Please contact your system administrator.
Add correct host key in /Users/giyad/.ssh/known_hosts to get rid of this message.
Offending key in /Users/giyad/.ssh/known_hosts:4
RSA host key for 192.168.15.200 has changed and you have requested strict checking.
Host key verification failed.
sed: .bx200811211126/console.log: No such file or directory
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
8e:ea:1e:de:d6:7d:2c:29:74:cb:0f:aa:e2:55:0e:06.
Please contact your system administrator.
Add correct host key in /Users/giyad/.ssh/known_hosts to get rid of this message.
Offending key in /Users/giyad/.ssh/known_hosts:4
RSA host key for 192.168.15.200 has changed and you have requested strict checking.
Host key verification failed.
sed: .bx200811211126/boxee.*: No such file or directory
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
8e:ea:1e:de:d6:7d:2c:29:74:cb:0f:aa:e2:55:0e:06.
Please contact your system administrator.
Add correct host key in /Users/giyad/.ssh/known_hosts to get rid of this message.
Offending key in /Users/giyad/.ssh/known_hosts:4
RSA host key for 192.168.15.200 has changed and you have requested strict checking.
Host key verification failed.
sed: .bx200811211126/CrashReporter.log: No such file or directory
tar: .bx200811211126/*: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors

Any suggestions? Didn't always use to do this, before it would complete but still nothing would be in the tgz. But one step at a time...

pkeenan
November 21st, 2008, 12:52 PM
GIYAD,

As I understand it you will need to either run one of these two scripts in Terminal to erase that message:


rm -f ~/.ssh/known_hosts
or
rm ~/.ssh/known_hosts

Anyone out there with a little SSH bravado care to back me up on this?

Peter

giyad
November 21st, 2008, 01:48 PM
GIYAD,

As I understand it you will need to either run one of these two scripts in Terminal to erase that message:


rm -f ~/.ssh/known_hosts
or
rm ~/.ssh/known_hosts

Anyone out there with a little SSH bravado care to back me up on this?

Peter
can someone confirm that please before i run it? thanks!

jdarnold
November 21st, 2008, 02:33 PM
You can always just move it. 'rm -f' just says to "force" the removal of the file. Safer would be to just move it:

mv ~/.ssh/known_hosts ~

This moves the 'known_hosts' file to your home folder (~). I think this will just force a re-verification. If something goes horribly wrong, you can always move it back:

mv ~/known_hosts ~/.ssh

giyad
November 21st, 2008, 07:08 PM
You can always just move it. 'rm -f' just says to "force" the removal of the file. Safer would be to just move it:

mv ~/.ssh/known_hosts ~

This moves the 'known_hosts' file to your home folder (~). I think this will just force a re-verification. If something goes horribly wrong, you can always move it back:

mv ~/known_hosts ~/.ssh
Thanks guys... I did that, and here are my results from running the script. Still nothing is in the tgz when I try to open it.

Last login: Fri Nov 21 19:04:52 on ttys000
Macz-2:~ giyad$ cd boxeelogs
Macz-2:boxeelogs giyad$ ./getboxeelogs.sh
Welcome to the AppleTV (via atv-usbcreator)
frontrow@192.168.15.200's password:
console.log 100% 224KB 224.2KB/s 00:00
Welcome to the AppleTV (via atv-usbcreator)
frontrow@192.168.15.200's password:
boxee.log 100% 37KB 37.1KB/s 00:00
boxee.old.log 100% 53KB 52.5KB/s 00:00
Welcome to the AppleTV (via atv-usbcreator)
frontrow@192.168.15.200's password:
CrashReporter.log 100% 68KB 67.5KB/s 00:00
.bx200811211906/CrashReporter.log
.bx200811211906/boxee.*
.bx200811211906/console.log

neobart
November 24th, 2008, 09:39 AM
OK help me out here.

When following the guide at the top of this thread all I get is.

ssh: connect to host port 22: Connection refused
ssh: connect to host port 22: Connection refused
ssh: connect to host port 22: Connection refused
ssh: connect to host port 22: Connection refused
tar: console.log: Cannot stat: No such file or directory
tar: CrashReporter.log: Cannot stat: No such file or directory
tar: boxee.log: Cannot stat: No such file or directory
tar: boxee.old.lo: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors

Has something changed since it can't find the logs?

Edit: Nevermind. I forgot to input my atv's address. I'm a dunce.

DuraCELL
December 5th, 2008, 03:28 AM
I'm thinking that a standard bug reporting feature to help getting the bug's out of Boxee would be a nice touch.

My initial idea was to have something similar to the Windows feature that just uploads the memory dump and/or the log file from the last crash.

However my most common bug so fare prevents me from starting Boxee all together, so I'm thinking is it possible just to have a standard bug reporting form.
A form would make it easy for use to report bugs back to you and it would make it easy for you guys on the Dev team to index the bugs and sort the log data associated with the bug's.
You would also be able to have special form's associated with different error messages to collect special data associated with just that bug :cool:

I hope it helps.
Chris

giyad
December 5th, 2008, 10:04 AM
I'm thinking that a standard bug reporting feature to help getting the bug's out of Boxee would be a nice touch.

My initial idea was to have something similar to the Windows feature that just uploads the memory dump and/or the log file from the last crash.

However my most common bug so fare prevents me from starting Boxee all together, so I'm thinking is it possible just to have a standard bug reporting form.
A form would make it easy for use to report bugs back to you and it would make it easy for you guys on the Dev team to index the bugs and sort the log data associated with the bug's.
You would also be able to have special form's associated with different error messages to collect special data associated with just that bug :cool:

I hope it helps.
Chris
+1, it would make it a lot easier, but then we don't get any goodies :(

darryldale
December 12th, 2008, 10:33 AM
After submitting a bug report to the address mentioned in the beginning of this thread should we expect a response indicating it was received?

I had previously started a thread on SMB shares and submitted a bug report as requested but have no idea if it was received, if it's a valid bug, etc......

Darryl

imksn
December 13th, 2008, 10:57 AM
whenever your boxee on atv goes into an error


Does that include freezing on exit?

imksn
December 13th, 2008, 11:23 AM
Well I tried the terminal command for the first time. I did something wrong because it seems to be doing something throughout my entire local hard disk instead of the networked aTV. Has been scrolling stuff like ./music/iTunes/iTunes music/.... and things like that for several minutes. What do I do to get this to stop?

imksn
December 30th, 2008, 01:05 AM
Well, it happened again. I ran the following commands and it looks like terminal is scanning my entire computer.

scp frontrow@{atv ip}:/Library/Logs/Console/501/console.log .
scp frontrow@{atv_ip}:/Users/frontrow/Library/Logs/CrashReporter/CrashReporter.log .
scp frontrow@{atv_ip}:/Users/frontrow/Library/Logs/boxee.log .
scp frontrow@{atv_ip}:/Users/frontrow/Library/Logs/boxee.old.log .
tar cvzf {atv_username}_atv.tgz console.log CrashReporter.log boxee.log boxee.old.log .

Last time it filled my hard disk with data. I haven't been given any way to stop this nor any help to get this right.

Someone kindly sent me a personal reply April 2009 that I just found in my personal messages file. Here is what's supposed to be my problem...

phliKtid
Junior Member

Join Date: Apr 2009
Posts: 0
your problem with the script to grab and tar log files on appletv
hey, you may have already figured it out or been told this, but i thought just in case (since i didn't see it in the thread) i would mention this...

the version of the tar command (the last line) you typed looked like this:

tar cvzf {atv_username}_atv.tgz console.log CrashReporter.log boxee.log boxee.old.log .

the problem is that period at the end. what that command is doing is telling tar to write to the file {atv_username}_atv.tgz all of the files listed. the problem is a period means "where i currently am". by default, when you open a terminal window you are in your home directory. that includes all your docs, pics, itunes library, etc. so effectively you told tar to backup the log files you listed, as well as the directory you are currently in.

if you get rid of that period you should be fine. i hope my explanation makes sense. : )

-phliKtid

silverhack
December 30th, 2008, 02:01 PM
Well, it happened again. I ran the following commands and it looks like terminal is scanning my entire computer.

scp frontrow@{atv ip}:/Library/Logs/Console/501/console.log .
scp frontrow@{atv_ip}:/Users/frontrow/Library/Logs/CrashReporter/CrashReporter.log .
scp frontrow@{atv_ip}:/Users/frontrow/Library/Logs/boxee.log .
scp frontrow@{atv_ip}:/Users/frontrow/Library/Logs/boxee.old.log .
tar cvzf {atv_username}_atv.tgz console.log CrashReporter.log boxee.log boxee.old.log .

Last time it filled my hard disk with data. I haven't been given any way to stop this nor any help to get this right.

You can't just copy and paste the commands directly - you have to change {atv ip} to be the IP address of your appletv and {atv_username} to be the username. If you're not sure what it is - look it up under the network settings in boxee. Otherwise, you can substitute 'appletv.local' for the IP.
So, the command would look more like:

scp frontrow@appletv.local:/Library/Logs/Console/501/console.log .
scp frontrow@appletv.local:/Users/frontrow/Library/Logs/CrashReporter/CrashReporter.log .
scp frontrow@appletv.local:/Users/frontrow/Library/Logs/boxee.log .
scp frontrow@appletv.local:/Users/frontrow/Library/Logs/boxee.old.log .
tar cvzf imksn_atv.tgz console.log CrashReporter.log boxee.log boxee.old.log

That will grab the files off the appletv, store them on your mac, and then put them together in a tarball (like a zip file) which you can then send in.

imksn
December 30th, 2008, 07:57 PM
- you have to change {atv ip} to be the IP address of your appletv and {atv_username} to be the username.

Actually, that's what I did. Just didn't feel secure to put that in public. The logs seem to download to my mac fine. It's just the last command that seems to start going through the entire hard disk. Made a file 10gb large. When I just took the separate logs off the mac and compressed in a folder, it was only kb's large. Also, are you supposed to be able to copy and paste all 4 lines of code into terminal? It only takes one at a time. So, when I put in the final line, it starts going through the whole hard disk.

clairehuxtable
April 9th, 2009, 01:16 PM
I just got hit with an error 11 after boxee quit on me. I am running the latest build.

ZombieSkin
April 10th, 2009, 02:38 PM
I had boxee uninstall itself after updating to the latest build. At least it's not showing up anymore. :confused:

tarquesh
April 15th, 2009, 06:03 PM
I will check it. Than report.

ejpring
April 30th, 2009, 10:41 AM
The shell script for collecting logs with 'scp' did not quite work for me -- the file pattern "boxee.*" causes 'scp' to overlay 'boxee.log' with 'boxee.old.log".

I have modified the script to fix this problem, and apply 'sed' only to the files that are actually collected:


#!/bin/bash

# declare the target machine and usernames this script needs

ATV=AppleTV.local # ... the IP name or address of your AppleTV machine
ATVUSER=frontrow # ... Boxee's account name on your AppleTV machine
BOXEEUSER=whatever # ... your account name at http://boxee.tv

# declare the log files this script will collect from the target machine

FILES="${FILES} /Library/Logs/Console/501/console.log"
FILES="${FILES} /Users/${ATVUSER}/Library/Logs/boxee.*"
FILES="${FILES} /Users/${ATVUSER}/Library/Logs/CrashReporter/CrashReporter.log"

# derive some internal variables

NOW=`date "+%Y%m%d_%H%M"`
TEMPDIR=".BoxeeLogs_${NOW}"
PACKAGE="BoxeeLogs_${NOW}_${BOXEEUSER}.tgz"

# collect the log files in a temporary directory, and then cleanse them

echo "collecting log files from ${ATV} ..."
mkdir ${TEMPDIR}
for f in ${FILES} ; do scp ${ATVUSER}@${ATV}:${f} ${TEMPDIR} ; done

echo "cleansing 'username:password' from collected log files ..."
for f in ${TEMPDIR}/* ; do sed -i '' "s/:\/\/.*:.*@/:\/\/XXX:XXX@/g" ${f} ; done

# pack the collected log files for delivery

echo "packing collected log files into ${PACKAGE} ..."
tar cvzf ${PACKAGE} ${TEMPDIR}/*
rm -rf ${TEMPDIR}


-- Ed

judgeschambers
June 28th, 2009, 09:02 AM
FYI,

Sent ATV Error Log file to Boxee email on Post #1. Topic is mostly SMB share and file name issues with crash error #4.

BinLeenk
July 26th, 2009, 03:15 PM
hey, I got an error 4 on Login.

giyad
November 4th, 2009, 07:43 PM
you need to set the atv ip for ATV= and your boxee user for BOXEEUSER=

yes, this script will cleanup your username/password

after saving the script, run it from terminal using sh ./getboxeelogs.sh
hey, when i run the scripts I get a resulting tgz file, and in the process through terminal I also see that everything is working... but when I try to unarchive the resulting tgz, i get nothing. It pretends like its untaring but no files come out..

When I don't use the scripts it works fine... Whats the deal?

tigeredwards
September 29th, 2010, 10:42 PM
good,thanks for sharing

mercyjan
November 9th, 2010, 03:18 AM
hi,'

hey, I got an error 4 on Login.