[Netarchivesuite-users] Problems With the HarvestController With 4.4.1

[Søren Vejrup Carlsen]

Hi Charles.
We are currently investigating the problem. 
So please be patient.

The cause is at first sight, that the attempt by the harvester to register itself fails. 
Reason why is that the response message is invalid. Why this is so, I don't know.

There could be some information in the HarvestJobManagerApplication logs as to why the registering fails?

Best regards

Søren V. Carlsen

________________________________________
Fra: NetarchiveSuite-users [netarchivesuite-users-bounces at ml.sbforge.org] på vegne af Charles Tassell [charles at islandadmin.ca]
Sendt: 2. december 2014 14:08
Til: netarchivesuite-users at ml.sbforge.org
Emne: [Netarchivesuite-users] Problems With the HarvestController With  4.4.1

Hi Everyone,

   Sorry if this is a dupe, I posted it to the list yesterday but I
don't think it went through as I wasn't subscribed.

   I've recently been trying to get NetArchiverSuite 4.4.1 running but
I'm not having much luck, and it seems to be related to the interaction
between the controllers and the message broker service. Whenever I start
the high/low controller processes I get the following in the startup logs:

Starting
dk.netarkivet.harvester.harvesting.distribute.HarvestControllerServer
Version: 4.4.1 status RELEASE
dk.netarkivet.harvester.harvesting.distribute.HarvestControllerServer
Running
1-Dec-2014 10:49:53 AM
dk.netarkivet.harvester.harvesting.distribute.HarvestControllerServer visit
SEVERE: Received message stating that channel 'HIGHPRIORITY' is invalid.
Will stop.

Starting
dk.netarkivet.harvester.harvesting.distribute.HarvestControllerServer
Version: 4.4.1 status RELEASE
dk.netarkivet.harvester.harvesting.distribute.HarvestControllerServer
Running
1-Dec-2014 10:49:53 AM
dk.netarkivet.harvester.harvesting.distribute.HarvestControllerServer visit
SEVERE: Received message stating that channel 'LOWPRIORITY' is invalid.
Will stop.

   I saw an earlier post from October where Mikis recommended restarting
the broker and making sure the queue was clear.  I did that but the
problem persists.  Any ideas as to how to fix it?  When I look at the
broker logs I see the system auto-creating queues like
HOSTNAME_COMMON_THIS_REPOS_CLIENT_IP_HCS_HIGH but no HIGHPRIORITY or
LOWPRIORITY so I'm wondering if I need to create some sort of user
accounts on the broker for the system to be able to register the channels.

   Oh, and on another note, in the 4.4.1 deployment script the log and
conf directories are not created automatically, which causes the install
to fail (the start/kill scripts and config settings aren't copied
over.)  I manually fixed this on my system during the install process
but I thought I should mention it.

_______________________________________________
NetarchiveSuite-users mailing list
NetarchiveSuite-users at ml.sbforge.org
http://ml.sbforge.org/mailman/listinfo/netarchivesuite-users