Ram,

> If Historical is set to true, how long each item is stored in the DB
> before actually purged? If the items are not purged, how to tackle
> the ever increasing DB? I am using version 0.3.

In nntp//rss v0.3, the historical flag means that items are permanently kept
in the database.

You can take a look at the following forum post that describes how to
manually purge items from the database:

http://www.methodize.org/forum/viewtopic.php?t=28

However, I'd recommend that you consider upgrading to nntp//rss v0.5b1.
Aside from a number of new features, it now supports expiration times for
historical articles, and will automatically purge those from the database.

Regards,

Jason

If Historical is set to true, how long each item is stored in the DB
before actually purged? If the items are not purged, how to tackle
the ever increasing DB? I am using version 0.3.

Thanks,
Ram

Greg,

>     Thanks for that link.  I found a bunch of /*C3*/ through /*C6*/
> strings in that file.  I removed them, but it's still having the same
> problem.  Is there a way to narrow down where the corrupt data is?
> FWIW, my .scripts file is 12 MB and I notice that NNTPRSS dies on
> startup after 2.5 minutes at ~95% CPU.   For kicks, I copied the files
> to the 0.5b folder and it started, but all my channels were missing.
> Is there a way to salvage my channel info from my 0.3 install?

Usually the corrupt data is at the end of the file.  I would not remove
anything in the middle of the file, especially if there is good content
after the commands.

If you want, you can ftp me a copy of the original hsqldb files, and I'll
take a look.  Email me off-list (jason at methodize.org) if you are
interested, and I'll give you the FTP details.

Regards,

Jason

On Mon, 13 Dec 2004 09:00:29 -0500, Jason Brome <jason@...> wrote:
>
> Greg,
>
> > Unexpected token: Unexpected token: TRSET in statement [SET AUTOCOMMIT
> > TRSET AUTOCOMMIT TRUE]
>
> It sounds like your hsqldb data file has some corrupt data.  Typically this
> Take a look at the following post on the nntp//rss message forum:
>
> http://www.methodize.org/forum/viewtopic.php?t=21
>
> Jason


Hi Jason-
      Thanks for that link.  I found a bunch of /*C3*/ through /*C6*/
strings in that file.  I removed them, but it's still having the same
problem.  Is there a way to narrow down where the corrupt data is?
FWIW, my .scripts file is 12 MB and I notice that NNTPRSS dies on
startup after 2.5 minutes at ~95% CPU.   For kicks, I copied the files
to the 0.5b folder and it started, but all my channels were missing.
Is there a way to salvage my channel info from my 0.3 install?

Thanks again,
Greg

Jason wrote:

>Hein,
>
>
>
>>--- In nntprss@yahoogroups.com, Aleksander Slominski <aslom@c...>
>>
>>
>wrote:
>
>
>>>it seems (?) you need to confirm you are  over 18 to see it and
>>>
>>>
>if
>
>
>>there
>>
>>
>>>is no cookie to prove it shows HTML page.
>>>
>>>
>>:-( any easy workaround for nntp//rss?
>>
>>
>
>Nothing that I can think of off the top of my head - however I'll
>look into how I could support capturing cookie information from the
>user, and passing it as part of the request.  The only slighty
>awkward part would be extracting the cookie information from your
>browser.
>
>
if  apache httpclient supports cookies then it may be a solution to read
results of ATOM pull - if it is HTML page then send POST with form data
and use cookie to pull ATOM again - not an easy process and hardly one
that can be automated ...

it would be easier if google groups could support in future HTTP Basic
Authorization for this kind of feeds so you can send "yes" password (or
something like that).

alek

>Jason
>
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>


--
The best way to predict the future is to invent it - Alan Kay

Hein,

> --- In nntprss@yahoogroups.com, Aleksander Slominski <aslom@c...>
wrote:
> > it seems (?) you need to confirm you are  over 18 to see it and
if
> there
> > is no cookie to prove it shows HTML page.
>
> :-( any easy workaround for nntp//rss?

Nothing that I can think of off the top of my head - however I'll
look into how I could support capturing cookie information from the
user, and passing it as part of the request.  The only slighty
awkward part would be extracting the cookie information from your
browser.

Does anyone know if it is the same cookie across all of the groups?

Jason

Greg,

> 08:05:09,646 [main] INFO  Main - Starting nntp//rss v0.3
> 08:07:36,417 [main] ERROR Main - Exception thrown during startup
> org.apache.commons.dbcp.DbcpException: java.sql.SQLException:
> Unexpected token: Unexpected token: TRSET in statement [SET AUTOCOMMIT
> TRSET AUTOCOMMIT TRUE]

It sounds like your hsqldb data file has some corrupt data.  Typically this
happens right at the end of the script, usually due to some form of unclean
shutdown or termination of the nntp//rss process.

Take a look at the following post on the nntp//rss message forum:

http://www.methodize.org/forum/viewtopic.php?t=21

Basically you just need to perform some slight pruning on the hsqldb.script
(after making a backup), to remove the corrupt entries at the end.  This
should allow you to successfully restart nntp//rss.

Once you've been able to restart with the fixed hsqldb files, I would
recommend upgrading to nntp//rss v0.5-beta-1, by copying those fixed hsqldb
files into the 0.5 directory.

Jason

I've been using 0.3 for quite a while and it's been working great.
Last night when I rebooted by PC (after I removed a
firewall/antivirus) program, NNTPRSS wouldn't start.  I am using a
shortcut that calls: C:\WINDOWS\system32\javaw.exe -jar "C:\Program
Files\nntprss\nntprss-start.jar"

I get the following error message in the log:

08:05:09,646 [main] INFO  Main - Starting nntp//rss v0.3
08:07:36,417 [main] ERROR Main - Exception thrown during startup
org.apache.commons.dbcp.DbcpException: java.sql.SQLException:
Unexpected token: Unexpected token: TRSET in statement [SET AUTOCOMMIT
TRSET AUTOCOMMIT TRUE]
{Full error log at bottom of message}

I downloaded 0.5beta and extracted it to a different folder and it
worked, but when I copied the 4 files listed in the Readme so I could
retain my archive I get the same error message.

Is there a way to save my archive?  If not, is there at least a way to
save my channel config (needless to say, NNTPRSS won't run, so I can't
backup).

Thanks for the help,
Greg


08:05:09,646 [main] INFO  Main - Starting nntp//rss v0.3
08:07:36,417 [main] ERROR Main - Exception thrown during startup
org.apache.commons.dbcp.DbcpException: java.sql.SQLException:
Unexpected token: Unexpected token: TRSET in statement [SET AUTOCOMMIT
TRSET AUTOCOMMIT TRUE]
	 at
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverMa\
nagerConnectionFactory.java:101)
	 at
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionF\
actory.java:184)
	 at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(Unknown
Source)
	 at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:146)
	 at java.sql.DriverManager.getConnection(Unknown Source)
	 at java.sql.DriverManager.getConnection(Unknown Source)
	 at
org.methodize.nntprss.rss.db.ChannelManagerDAO.initialize(ChannelManagerDAO.java\
:311)
	 at org.methodize.nntprss.db.DBManager.configure(DBManager.java:125)
	 at org.methodize.nntprss.Main.startNntpRss(Main.java:106)
	 at org.methodize.nntprss.Main.main(Main.java:172)
	 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	 at java.lang.reflect.Method.invoke(Unknown Source)
	 at org.methodize.nntprss.Startup.run(Startup.java:104)
	 at org.methodize.nntprss.Startup.main(Startup.java:66)
Caused by: java.sql.SQLException: Unexpected token: Unexpected token:
TRSET in statement [SET AUTOCOMMIT TRSET AUTOCOMMIT TRUE]
	 at org.hsqldb.Trace.getError(Unknown Source)
	 at org.hsqldb.Log.runScript(Unknown Source)
	 at org.hsqldb.Log.open(Unknown Source)
	 at org.hsqldb.Database$Logger.openLog(Unknown Source)
	 at org.hsqldb.Database.open(Unknown Source)
	 at org.hsqldb.Database.<init>(Unknown Source)
	 at org.hsqldb.jdbcConnection.openStandalone(Unknown Source)
	 at org.hsqldb.jdbcConnection.<init>(Unknown Source)
	 at org.hsqldb.jdbcDriver.connect(Unknown Source)
	 at java.sql.DriverManager.getConnection(Unknown Source)
	 at java.sql.DriverManager.getConnection(Unknown Source)
	 at
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverMa\
nagerConnectionFactory.java:95)
	 ... 15 more

--- In nntprss@yahoogroups.com, Aleksander Slominski <aslom@c...> wrote:
> it seems (?) you need to confirm you are  over 18 to see it and if
there
> is no cookie to prove it shows HTML page.

:-( any easy workaround for nntp//rss?

Thanks,
Hein

hp_roehrig wrote:

>According to
>
>http://groups-beta.google.com/group/plan9dev/about
>
>the following link should be in Atom format:
>
>http://groups-beta.google.com/group/plan9dev/feed/msgs.xml
>
>However, nntp//rss v0.5-beta-1 chokes on it, as does the offered
>validation link. Could it be that Google is doing some magic on the
>user-agent header to decide whether to serve XML or HTML?
>
>
it seems (?) you need to confirm you are  over 18 to see it and if there
is no cookie to prove it shows HTML page.

alek

--
The best way to predict the future is to invent it - Alan Kay

According to

http://groups-beta.google.com/group/plan9dev/about

the following link should be in Atom format:

http://groups-beta.google.com/group/plan9dev/feed/msgs.xml

However, nntp//rss v0.5-beta-1 chokes on it, as does the offered
validation link. Could it be that Google is doing some magic on the
user-agent header to decide whether to serve XML or HTML?

Thanks,
Hein

Hein,

Does this exception always happen when polling those two channels, or were
they sporadic exceptions?

Jason

----- Original Message -----
From: "Hein Roehrig" <yahoogroups@...>
To: <nntprss@yahoogroups.com>
Sent: Tuesday, November 16, 2004 2:11 AM
Subject: [nntprss] Re: various problems with v0.5-beta-1


>
> Some more interesting error messages:
>
> 23:17:02,106 [Channel Poll Worker #3] WARN  Channel -
> Channel=com.fastmail.status - NoClassDefFound
> java.lang.NoClassDefFoundError: L@^\
...
> The ^\ in "L@^\" stands for a non-printable ASCII character...
>
> And another one:
>
> 23:17:06,322 [Channel Poll Worker #2] WARN  Channel -
> Channel=people.schneier.crypto-gram - Exception while polling channel
> java.lang.NullPointerException
...

Hein,

First - there is now a patched nntprss.jar module available for migrating
jdbm entries to Derby.  Please check the following forum posting:

http://www.methodize.org/forum/viewtopic.php?t=62#202

When you say nntp//rss locks up - is this the whole processing?  Polling?
or always just article retrieval?

What version of Java 1.5 do you having running on your Linux server?  Is it
possible for you to test nntp//rss on Debian with a 1.4 JRE?  I'm not
familiar with the SQL Exception mentioned in your original post - though
this hints at some type of corruption.  I will investigate.  There are a
group of tools available for manipulating Derby databases.  They ship with
the standard Derby distribution - take a look at
http://incubator.apache.org/derby for more information.

Jason

> I upgraded from a v0.4 from CVS to v0.5-beta-1 from the web. In the
> process I discarded my old database (is there a way to go from JDBM to
> Derby?) Now nntp//rss locks up frequently--most of the time, everything
> seems to work except that retrieving an actual article blocks
> indefinitely. I was going to analyze this in more detail (I'm not used
> to debugging Java) but now I got this:
>
> java.lang.RuntimeException: SQL Exception: An internal error was
> identified by RawStore module.
>
> I would greatly welcome any debugging hints. Can the database be dumped?
> How do you analyze deadlocks?
>
> All this is on a colocated Debian-unstable Linux server with Java 1.5.

Some more interesting error messages:

23:17:02,106 [Channel Poll Worker #3] WARN  Channel -
Channel=com.fastmail.status - NoClassDefFound
java.lang.NoClassDefFoundError: L@^\
         at
        
org.apache.commons.httpclient.HeaderGroup.getHeaders(HeaderGroup.java:177)
         at
        
org.apache.commons.httpclient.HttpMethodBase.setRequestHeader(HttpMethodBase.jav\
a:528)
         at
        
org.apache.commons.httpclient.HttpMethodBase.setRequestHeader(HttpMethodBase.jav\
a:517)
         at org.methodize.nntprss.feed.Channel.poll(Channel.java:250)
         at org.methodize.nntprss.feed.Channel.run(Channel.java:762)
         at
        
org.methodize.nntprss.util.FixedThreadPool$WorkerThread.run(FixedThreadPool.java\
:89)

The ^\ in "L@^\" stands for a non-printable ASCII character...

And another one:

23:17:06,322 [Channel Poll Worker #2] WARN  Channel -
Channel=people.schneier.crypto-gram - Exception while polling channel
java.lang.NullPointerException
         at
        
org.apache.log4j.AppenderSkeleton.isAsSevereAsThreshold(AppenderSkeleton.java:18\
9)
         at
         org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:206)
         at
        
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAt\
tachableImpl.java:57)
         at org.apache.log4j.Category.callAppenders(Category.java:187)
         at org.apache.log4j.Category.forcedLog(Category.java:372)
         at org.apache.log4j.Category.log(Category.java:864)
         at
        
org.apache.commons.logging.impl.Log4JCategoryLog.trace(Log4JCategoryLog.java:148\
)
         at
        
org.apache.commons.httpclient.HttpConnection.print(HttpConnection.java:1018)
         at
        
org.apache.commons.httpclient.HttpMethodBase.writeRequestHeaders(HttpMethodBase.\
java:2330)
         at
        
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:22\
13)
         at
        
org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:\
2571)
         at
        
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1047)
         at
        
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:638)
         at
        
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:526)
         at
         org.methodize.nntprss.feed.Channel.executeHttpRequest(Channel.java:1053)
         at org.methodize.nntprss.feed.Channel.poll(Channel.java:279)
         at org.methodize.nntprss.feed.Channel.run(Channel.java:762)
         at
        
org.methodize.nntprss.util.FixedThreadPool$WorkerThread.run(FixedThreadPool.java\
:89)

Hello *,

I upgraded from a v0.4 from CVS to v0.5-beta-1 from the web. In the
process I discarded my old database (is there a way to go from JDBM to
Derby?) Now nntp//rss locks up frequently--most of the time, everything
seems to work except that retrieving an actual article blocks
indefinitely. I was going to analyze this in more detail (I'm not used
to debugging Java) but now I got this:

java.lang.RuntimeException: SQL Exception: An internal error was
identified by RawStore module.

I would greatly welcome any debugging hints. Can the database be dumped?
How do you analyze deadlocks?

All this is on a colocated Debian-unstable Linux server with Java 1.5.

Thanks,
Hein

i think it would be great to add support for
http://developers.technorati.com/wiki/attentionxml

if i have some time (unlikely but who knows) i may actually implement it
especially if there ate cool aggregator sites or tools to use ....

alek

Jason Brome wrote:
> Example ItemProcessors could include an Item emailer, archiver, or, as
> described in your email, something that fetches the article's full content
> and updates the description before it gets persisted by nntp//rss to the
> database.  I could envision building an Item emailer that looked for certain
> phrases within the Item content, and, if matched, would send an email or a
> message to a cellphone.
>
> Jason


Excellent.


BoD

BoD,

> Also, while we are talking about feature requests ;) posting the
> articles to a maildir, or to an email address would be ultimate-cool !

Thanks for the suggestions - I'll keep them in mind for future feature
enhancements.

One thing that will be appearing in the short term (hopefully by the next
0.5 beta) will be the concept of an ItemProcessor plug-in.  This will allow
people to create a plug-in class that sits in the item processing pipeline.
When new or updated items are received, the ItemProcessor's onItem method
will be invoked.

Example ItemProcessors could include an Item emailer, archiver, or, as
described in your email, something that fetches the article's full content
and updates the description before it gets persisted by nntp//rss to the
database.  I could envision building an Item emailer that looked for certain
phrases within the Item content, and, if matched, would send an email or a
message to a cellphone.

Jason

By the way, what would be more interesting, I think, is an option to
post the content pointed at by the permalink, instead of the content of
the "description" element.
Some blogs don't have any description at all, or just the first few
words, so you have to go to the website to see the actual article (thus
losing the advantage of nntp//rss).

Firefox has a similar option in their rss module (uncheck "Show the
article summary instead of loading the web page"), and it is very
convenient.


Also, while we are talking about feature requests ;) posting the
articles to a maildir, or to an email address would be ultimate-cool !

Thanks.

BoD


Jason Brome wrote:
> Hi,
>
> I've just placed a poll on the nntp//rss message boards regarding support
> for RSS enclosures.  Please take a look and give me your feedback.
>
> http://methodize.org/forum/viewtopic.php?t=63
>
> Thanks,
>
> Jason
>
> --
> Jason Brome
> jason@...
>

Hi,

I've just placed a poll on the nntp//rss message boards regarding support
for RSS enclosures.  Please take a look and give me your feedback.

http://methodize.org/forum/viewtopic.php?t=63

Thanks,

Jason

--
Jason Brome
jason@...

Alan,

> > Was this process started with nohup?  If so, can you take a look in the
> > nohup.out file and see if there are any exceptions.
>
> no it wasn't created with nohup.

Right now I am not sure what is causing the process to shutdown.  I have had
v0.5 beta 1 running on a SuSE 9.1 setup without experience the same results.
I would suggesting running it with nohup, and seeing how it behaves -
hopefully this will trap any malignant signals and ensure that the process
stays up.

Jason

Jason Brome wrote:
> Alan,
>
> ----- Original Message -----
>  > the log.log doesn't show anything other than i showed you this morning.
>  >
>  > no shell was logged out.
>  >
>  > very weird.  i didn't have this issue with 0.4; and it was on the same
>  > box.
>
> Was this process started with nohup?  If so, can you take a look in the
> nohup.out file and see if there are any exceptions.

no it wasn't created with nohup.

Alan,

----- Original Message -----
> the log.log doesn't show anything other than i showed you this morning.
>
> no shell was logged out.
>
> very weird.  i didn't have this issue with 0.4; and it was on the same
> box.

Was this process started with nohup?  If so, can you take a look in the
nohup.out file and see if there are any exceptions.

Thanks,

Jason

if you upgraded (as i did) to MySQL 4.1.x and as well upgraded mysql
authentication then you /may/ need GRANT again priviliges (it mysql db
tables are flushed) and as well you may need (not sure about this one)
to download the latest mysql-connector and overwrite ext/lib/mysql.jar -
this fixed problem for me (mysql conenctor 3.0.15-ga).

alek

otherwise you may be getting this:

org.apache.commons.dbcp.DbcpException: java.sql.SQLException: Server
connection failure during transaction. Due to underlying exception:
'java.sql.SQLException: Invalid authorization specification,  message
from server: "Access denied for user 'nntprss'@'localhost' (using
password: YES)"'.
Attempted reconnect 3 times. Giving up.
     at
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverMa\
nagerConnectionFactory.java:101)
     at
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionF\
actory.java:184)
     at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(Unknown Source)
     at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:146)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:193)
     at
org.methodize.nntprss.feed.db.JdbcChannelDAO.loadConfiguration(JdbcChannelDAO.ja\
va:333)
     at
org.methodize.nntprss.feed.ChannelManager.configure(ChannelManager.java:103)
     at org.methodize.nntprss.Main.startNntpRss(Main.java:136)
     at org.methodize.nntprss.Main.main(Main.java:201)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav\
a:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.methodize.nntprss.Startup.run(Unknown Source)
     at org.methodize.nntprss.Startup.main(Unknown Source)
Caused by: java.sql.SQLException: Server connection failure during
transaction. Due to underlying exception: 'java.sql.SQLException:
Invalid authorization specification,  message from server: "Access
denied for user 'nntprss'@'localhost' (using password: YES)"'.
Attempted reconnect 3 times. Giving up.
     at com.mysql.jdbc.Connection.createNewIO(Connection.java:1780)
     at com.mysql.jdbc.Connection.<init>(Connection.java:427)
     at
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:395)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:171)
     at
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverMa\
nagerConnectionFactory.java:95)
     ... 15 more


or this (with new driver):

org.apache.commons.dbcp.DbcpException: java.sql.SQLException: Server
connection failure during transaction. Due to underlying exception:
'java.sql.SQLException: Invalid authorization specification message from
server: "Access denied for user 'nntprss'@'localhost' (using password:
YES)"'.

** BEGIN NESTED EXCEPTION **

java.sql.SQLException
MESSAGE: Invalid authorization specification message from server:
"Access denied for user 'nntprss'@'localhost' (using password: YES)"

STACKTRACE:

java.sql.SQLException: Invalid authorization specification message from
server: "Access denied for user 'nntprss'@'localhost' (using password: YES)"
     at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1997)
     at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1906)
     at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:2520)
     at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:817)
     at com.mysql.jdbc.Connection.createNewIO(Connection.java:1898)
     at com.mysql.jdbc.Connection.<init>(Connection.java:450)
     at
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:411)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:171)
     at
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverMa\
nagerConnectionFactory.java:95)
     at
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionF\
actory.java:184)
     at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(Unknown Source)
     at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:146)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:193)
     at
org.methodize.nntprss.feed.db.JdbcChannelDAO.loadConfiguration(JdbcChannelDAO.ja\
va:333)
     at
org.methodize.nntprss.feed.ChannelManager.configure(ChannelManager.java:103)
     at org.methodize.nntprss.Main.startNntpRss(Main.java:136)
     at org.methodize.nntprss.Main.main(Main.java:201)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav\
a:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.methodize.nntprss.Startup.run(Unknown Source)
     at org.methodize.nntprss.Startup.main(Unknown Source)


** END NESTED EXCEPTION **


Attempted reconnect 3 times. Giving up.
     at
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverMa\
nagerConnectionFactory.java:101)
     at
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionF\
actory.java:184)
     at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(Unknown Source)
     at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:146)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:193)
     at
org.methodize.nntprss.feed.db.JdbcChannelDAO.loadConfiguration(JdbcChannelDAO.ja\
va:333)
     at
org.methodize.nntprss.feed.ChannelManager.configure(ChannelManager.java:103)
     at org.methodize.nntprss.Main.startNntpRss(Main.java:136)
     at org.methodize.nntprss.Main.main(Main.java:201)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav\
a:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.methodize.nntprss.Startup.run(Unknown Source)
     at org.methodize.nntprss.Startup.main(Unknown Source)
Caused by: java.sql.SQLException: Server connection failure during
transaction. Due to underlying exception: 'java.sql.SQLException:
Invalid authorization specification message from server: "Access denied
for user 'nntprss'@'localhost' (using password: YES)"'.

** BEGIN NESTED EXCEPTION **

java.sql.SQLException
MESSAGE: Invalid authorization specification message from server:
"Access denied for user 'nntprss'@'localhost' (using password: YES)"

STACKTRACE:

java.sql.SQLException: Invalid authorization specification message from
server: "Access denied for user 'nntprss'@'localhost' (using password: YES)"
     at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1997)
     at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1906)
     at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:2520)
     at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:817)
     at com.mysql.jdbc.Connection.createNewIO(Connection.java:1898)
     at com.mysql.jdbc.Connection.<init>(Connection.java:450)
     at
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:411)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:171)
     at
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverMa\
nagerConnectionFactory.java:95)
     at
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionF\
actory.java:184)
     at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(Unknown Source)
     at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:146)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:193)
     at
org.methodize.nntprss.feed.db.JdbcChannelDAO.loadConfiguration(JdbcChannelDAO.ja\
va:333)
     at
org.methodize.nntprss.feed.ChannelManager.configure(ChannelManager.java:103)
     at org.methodize.nntprss.Main.startNntpRss(Main.java:136)
     at org.methodize.nntprss.Main.main(Main.java:201)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav\
a:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.methodize.nntprss.Startup.run(Unknown Source)
     at org.methodize.nntprss.Startup.main(Unknown Source)


** END NESTED EXCEPTION **


Attempted reconnect 3 times. Giving up.
     at com.mysql.jdbc.Connection.createNewIO(Connection.java:1964)
     at com.mysql.jdbc.Connection.<init>(Connection.java:450)
     at
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:411)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:171)
     at
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverMa\
nagerConnectionFactory.java:95)
     ... 15 more




alek

the log.log doesn't show anything other than i showed you this morning.

no shell was logged out.

very weird.  i didn't have this issue with 0.4; and it was on the same box.

Alan,

> nohup?
>
> i started it with:
>
> /java/bin/java -jar nntprss-start.jar &

nohup will ensure that if the shell from which nntp//rss was started is
terminate (e.g. the user logged off), that the spawned process will not
received a hangup signal.  Does the time of nntp//rss shutting down coincide
with you logging off any terminal sessions?

The command line (given your example above) would be as follows:

nohup /java/bin/java -jar nntprss-start &

Jason

> One more question - did you start nntp//rss with nohup?

nohup?

i started it with:

/java/bin/java -jar nntprss-start.jar &

Alan,

One more question - did you start nntp//rss with nohup?

Jason

----- Original Message -----
> Ok - if it shuts down again, please email me a copy of the log.log file
from
> the nntp//rss root directory.  I will take a look in the code to see if I
> can find anything obvious that could cause this to happen.  Also, are
there
> any cron jobs scheduled to run around that time?  I'm wondering if there
> could be any conflicts.

thanks Jason.

[no crons btw. they all run at 0300 etc]

Jason Brome wrote:
> Alan,
>
>  > No nothing significant Jason.  It had just finished polling some feeds.
>  >
>  > The box itself was up and running with no problems.
>  >
>  > It had been running for approximately 18hrs at that point.
>  >
>  > I'll monitor it tonight to see what happens
>
> Ok - if it shuts down again, please email me a copy of the log.log file from
> the nntp//rss root directory.  I will take a look in the code to see if I
> can find anything obvious that could cause this to happen.  Also, are there
> any cron jobs scheduled to run around that time?  I'm wondering if there
> could be any conflicts.

Alan,

> No nothing significant Jason.  It had just finished polling some feeds.
>
> The box itself was up and running with no problems.
>
> It had been running for approximately 18hrs at that point.
>
> I'll monitor it tonight to see what happens

Ok - if it shuts down again, please email me a copy of the log.log file from
the nntp//rss root directory.  I will take a look in the code to see if I
can find anything obvious that could cause this to happen.  Also, are there
any cron jobs scheduled to run around that time?  I'm wondering if there
could be any conflicts.

Regards,

Jason