Help a noob?

[jbeezybaby]

Ok. Im not exactly what you would call tech savvy. My friend hooked me up with this and I love it. But all of a sudden i cant log on and we are on the outs so I have no tech support so to speak. I get a error - Oops! Google Chrome could not connect to 192.168.1.166:8080. When I turn on my computer I get a error window that states Error check c:\Program files (x86)\Sabnzbd\Sabnzbd.exelog. If anyone can help that would be great but please remember keep it simple im a bit ignorant when it comes to the innerworkings of these things.

[shypike]

Is there anything the said file c:\Program files (x86)\Sabnzbd\Sabnzbd.exe.log ?

[jbeezybaby]

Yes exactly. The message comes up every time i start up my computer

[shypike]

What's IN in the file?
Open it with notepad.

[jbeezybaby]

Sorry so long on the reply. Been a bit crazy. This is the Error I found "*******************************************
***          Known issues              ***
*******************************************

- When par2 or unrar hang up, never just stop SABnzbd.
  Instead use your operating system's task manager to stop the par2 or unrar program.
  Forcing SABnzbd to quit may damage your queues.
  Windows-only:
  If you keep having trouble with par2 multicore you can disable it
  in Config->Switches.
  This will force the use of the old and tried, but slower par2-classic program.

- Windows cannot handle pathnames longer than 254 characters.
  Currently, SABnzbd doesn't handle this problem gracefully.
  We have added the INI-only option "folder_length_max" in which you can set
  a maximum folder name size.
  For Windows the default is 128 and for others 256.
  A quite safe value for Windows would be 64.
  SABnzbd will take care of overlapping names.
  See: http://wiki.sabnzbd.org/configure-special

- Some Usenet servers have intermittent login (or other) problems.
  For these the server blocking method is not very favourable.
  There is an INI-only option that will limit blocks to 1 minute.
      no_penalties = 1
  See: http://wiki.sabnzbd.org/configure-special

- On OSX you will have problems running Python user scripts.
  This is caused by wrong behaviour of the Python-to-app converter we use.
  Currently we cannot fix this. As a work-around you need to add
  the -E parameter to the first line of your Python script.
  Example:
        #!/bin/python -E

- On OSX you may encounter downloaded files with foreign characters.
  The par2 repair may fail when the files were created on a Windows system.
  The problem is caused by the PAR2 utility and we cannot fix this now.
  This does not apply to files inside RAR files.

- On Linux when you download files they may have the wrong character encoding.
  You will see this only when downloaded files contain accented characters.
  You need to fix it yourself by running the convmv utility (availaible for most Linux platforms).

- The "Watched Folder" sometimes fails to delete the NZB files it has
  processed. This happens when other software still accesses these files.
  Some third-party utilities supporting SABnzbd are known to do this.
  We cannot solve this problem, because the Operating System (read Windows)
  prevents the removal.

- Jobs deleted from the queue will leave downloaded files behind
  in the "incomplete" folder.
  You will have to remove these files manually.

- Memory usage can sometimes have high peaks. This makes using SABnzbd on very low
  memory systems (eg a SAN device) a challenge.

- SABnzbd is not compatible with some software firewall versions.
  The Mircosoft Windows Firewall works fine, but remember to tell this
  firewall that SABnzbd is allowed to talk to other computers.

- When SABnzbd cannot send nofication emails, check your virus scanner,
  firewall or securiry suite. It may be blocking outgoing email.

- When you are using external drives or network shares on OSX or Linux
  make sure that the drives are mounted.
  The operating system wil simply redirect your files to alternative locations.
  You may have trouble finding the files when mounting the drive later.

- Sometimes logging stops. This is a notorious bug in Python logging. SABnzbd will
  function as normal. If you run from sources or use the --console option with the
  Win32-binary, you will see that logging continues in the console window, but
  nothing will be written to the log-files."

Needless to say..... I clueless.

[shypike]

What do you mean "Error I found"?
What you listed is the file ISSUES.txt, we wrote that!
You should have a look at sabnzbd.exe.log in the same folder.

[jbeezybaby]

You know what... Ive thought about this and I know Im a noob and thats why Im here asking for help. Now I would like to think that Im not being overly sensitive but YOU are coming across as a ARROGANT PRICK. I  would rather go back to manually downloading the files and extracting them myself then have to deal with assholes like you. Good Day......

[komugi]

You know what... Ive thought about this and I know Im a noob and thats why Im here asking for help. Now I would like to think that Im not being overly sensitive but YOU are coming across as a ARROGANT PRICK. I  would rather go back to manually downloading the files and extracting them myself then have to deal with assholes like you. Good Day......

That's a bit of an overreaction. He is simply telling you that you opened/pasted the wrong file. You need to find the sabnzbd.exe.log file and not the issues.txt file.

[jbeezybaby]

I thought so but then not really. I understand what he was asking but read that aloud to yourself.... I understand that these guys may have to deal with a lot of stupid questions but this was my first post and i need help, and for someone... i dont care if they are one of the Devs or not to act that way and show no empathy is a bit extreme. I stated in the original post that I wasnt tech savvy. Just seems very rude to someone reaching out for support in a new forum...

[shypike]

My simple question was:

Is there anything in the said file c:\Program files (x86)\Sabnzbd\Sabnzbd.exe.log ?

and

Open it with notepad.

The answer was a listing of another file.

If you still want help, I need to know what's in the file.
If not, that's OK with me too.

[pmow]

To answer your previous question, yes you are being overly sensitive.  If everyone else believes he was being reasonable, perhaps you are at fault.

If you call someone an "arrogant prick" while asking for help, you're doing it wrong.  Personally, if I were in Shypike's shoes, I would have told you to go screw yourself after what you responded.  That he decided to take the high road and be more mature than me (or you) is evocative of how much class many of the volunteers here have. 

[jbeezybaby]

What do you mean "Error I found"?
What you listed is the file ISSUES.txt, we wrote that!

My point was that this ^ sounded arrogant.... I personally dont see how one would read it any other way "!". Its neither here nor there.... And by the way pmow  at this point I was not asking nor did i want any help. If you are going to "volunteer" on a forum where you are listed as a developer then you should be a little more patient and not make it a point to type like a jerk. Its not as if you said something in the wrong tone and someone took it wrong... its deliberate.
Uninstalled.... Good day

[inpheaux]

Its not as if you said something in the wrong tone and someone took it wrong...

No, that's exactly what happened.

SABnzbd asked you to check the log. You didn't.
We asked you to check the log. You didn't.
We asked you again and told you exactly what to do. You opened the wrong file - even SAID it was the wrong file - and posted it anyway.
We told you it was the wrong file. You flipped out and started accusing us of being arrogant because shypike DARED to punctuate with an exclamation mark.

Sorry you're too sensitive to handle even the most simple and cordial support discussion. Good luck surviving out there on the internet, I hear it's full of surly ill-tempered individuals who might be mean to you!

(OH NO I USED AN EXCLAMATION MARK!)