On Sun, Dec 16, 2012 at 11:34 PM, Bart <
bartn...@gmail.com> wrote:
> It seemed like SS didn't get past the databases location.. So when i changed
> the permissions of database directory everything worked.
> (still reading in on what the right permissions are though..)
Thanks to Mark for reminding of permissions. I should have suggested
that apart from double checking that the path to database directory in
configuration file. But I still can't explain why SS would complain
about not being able to find configuration file _after_ discovering
the binaries. Incorrect permissions should raise `Errno::EACCES` and
SS should just abort.
> On Friday, December 14, 2012 11:26:18 PM UTC+1, Anurag Priyam wrote:
>
>> SS looks for configuration file in the home directory (same when writing
>> the dummy configuration file). Is your home directory /var/www? How come?
>
> /var/www is not my home directory.. i added the the line in
config.ru where
> the .sequenceserver.conf can be found.
Ah, right. SS actually writes the dummy config file to the path name
pointed to by 'config_file' variable. My bad.
>> If you can run `blastp` from your shell without typing in the absolute
>> path, SS will find it. Being able to find BLAST binaries is inconclusive to
>> say SS is reading the config file or not.
>
> blast runs the from the shell without the absolute path... But if SS is able
> to find it, why doesn't it find BLAST when the conf file is empty or only
> the database line is configured? (The difference between the empty and the
> configured file is one of the reasons i came to the conclusion SS could read
> it.)
It does. On the first run, it generates a dummy config file and
exits. If you run SS again without editing the config file, it will
detect BLAST (if it's in PATH) and even give you fire ant sequences to
play around with. Not sure what's tripping SS on your setup.
>> WARN -- : Empty configuration file:
>> /var/www/sequenceserver/.sequenceserver.conf - will assume default settings
>>
>> Could you make a pastie / gist out of the log file and post a link?
>
> (In case your still interested)
> Which log do you mean? The apache log doesn't give much more info then i
> already gave.
Yeah, I was referring to Apache log. You hand picked those lines from
there, right?
>> Line 194 on version 0.8.2 points to a different kind of error, which
>> should have been logged. What version of SS are you using?
>
> I am using 0.8.2 (cloned it from github)
Woah! This is a mess. Ok, please send me the Apache log file (gist / pastie).
> Thanks again and thank you for this great app :)
I am glad you like it :).
-- yeban