Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server Error (500) after emird restart #70

Open
valtri opened this issue Sep 11, 2012 · 6 comments
Open

Server Error (500) after emird restart #70

valtri opened this issue Sep 11, 2012 · 6 comments
Assignees

Comments

@valtri
Copy link
Member

valtri commented Sep 11, 2012

Hello,

emird stops working after first restart (probably after the service delete), and new service can't be posted even with different ID.

Log, json, and config below.

Frantisek

/var/log/emi/emird/emird.log:

2012-09-11 15:16:11,498 DEBUG EMIR service on url 'http://zam052v04.zam.kfa-juelich.de:54321' is running since Wed Jul 18 11:20:14 CEST 2012
2012-09-11 15:16:11,499 DEBUG Daemon starting...
2012-09-11 15:16:11,501 DEBUG Daemon started
2012-09-11 15:16:11,503 DEBUG Registering service entries
2012-09-11 15:16:11,504 DEBUG REGISTRATION: Endpoint ID: myriad5.zcu.cz_lbserver_org.glite.lb.Server; URL: https://myriad5.zcu.cz:9003
2012-09-11 15:17:45,957 DEBUG Deleting reqistered entries
2012-09-11 15:17:46,001 DEBUG Daemon stopping...
2012-09-11 15:17:46,001 DEBUG Daemon stopped
2012-09-11 15:17:48,070 DEBUG EMIR service on url 'http://zam052v04.zam.kfa-juelich.de:54321' is running since Wed Jul 18 11:20:14 CEST 2012 
2012-09-11 15:17:48,070 DEBUG Daemon starting...
2012-09-11 15:17:48,073 DEBUG Daemon started
2012-09-11 15:17:48,073 DEBUG Registering service entries
2012-09-11 15:17:48,075 DEBUG REGISTRATION: Endpoint ID: myriad5.zcu.cz_lbserver_org.glite.lb.Server; URL: https://myriad5.zcu.cz:9003 
2012-09-11 15:17:48,127 DEBUG Falling back to initial service entry update
2012-09-11 15:17:48,128 DEBUG REGISTRATION: Endpoint ID: myriad5.zcu.cz_lbserver_org.glite.lb.Server; URL: https://myriad5.zcu.cz:9003 
2012-09-11 15:17:48,178 ERROR Registration failed: Server Error (500): {}

/var/cache/emird/glite-lb-bkserver.json

{
        "Service_ID": "myriad5.zcu.cz_lbserver",
        "Service_Name": "emitb-Server", 
        "Service_Type": "org.glite.lb.Server",
        "Service_QualityLevel": "production",
        "Service_CreationTime": { "$date": "2012-09-11T13:16:11Z" },
        "Service_Endpoint_ID": "myriad5.zcu.cz_lbserver_org.glite.lb.Server",
        "Service_Endpoint_URL": "https://myriad5.zcu.cz:9003", 
        "Service_Endpoint_Capability": "information.logging",
        "Service_Endpoint_Technology": "webservice",
        "Service_Endpoint_InterfaceName": "org.glite.lb.Server", 
        "Service_Endpoint_InterfaceVersion": "3.4.4",
        "Service_Endpoint_ServingState": "production",
        "Service_Endpoint_QualityLevel": "production",
        "Service_Endpoint_WSDL": "http://egee.cesnet.cz/cms/export/sites/egee/en/WSDL/3.1/LB.wsdl"
}

/etc/emi/emird/emird.ini:

[emir]
url = http://zam052v04.zam.kfa-juelich.de:54321
period = 240
validity = 1440

#cert = /etc/grid-security/emi/hostcert.pem
#key = /etc/grid-security/emi/hostkey.pem
#cadir = /etc/grid-security/certificates

verbosity = debug

[advancedService]
json_file_location = /var/cache/emird/glite-lb-bkserver.json
@amemon
Copy link
Member

amemon commented Sep 12, 2012

Hi Frantisek, which version of emir server and emird have you installed? I assume the server version is 1.1.1 and emird is 1.0.0 right?

@ghost ghost assigned martonivan Sep 12, 2012
@martonivan
Copy link
Contributor

Hi!

It seams that the service deletion is failing ('cause a known incompatibility between the new service and the former client version that is already fixed in the new emir-serp version), then it tried to reregister it which fails since the entry is already in the EMIR database, so cannot be registered. (This behavior is also fixed in the new version.)

It would be recommended to upgrade emird to emir-serp 1.1.0.

@amemon
Copy link
Member

amemon commented Sep 12, 2012

The process to upgrade the GSR on zam052v04 will soon start.

On Wed, Sep 12, 2012 at 10:49 AM, martonivan [email protected]:

Hi!

It seams that the service deletion is failing ('cause a known
incompatibility between the new service and the former client version that
is already fixed in the new emir-serp version), then it tried to reregister
it which fails since the entry is already in the EMIR database, so cannot
be registered. (This behavior is also fixed in the new version.)

It would be recommended to upgrade emird to emir-serp 1.1.0.


Reply to this email directly or view it on GitHubhttps://github.com//issues/70#issuecomment-8486119.

@valtri
Copy link
Member Author

valtri commented Sep 12, 2012

Versions are: emird-1.0.1 (SL5) and emir-serp-1.1.0 from git (Debian). Behavior is the same, the newer version has better log:

2012-09-12 13:58:59,812 ERROR Connection failed to http://emiregistry2.grid.niif.hu:54321
2012-09-12 14:00:14,604 DEBUG EMIR service on url 'http://zam052v04.zam.kfa-juelich.de:54321' is running since Wed Jul 18 11:20:14 CEST 2012
2012-09-12 14:00:14,604 DEBUG Daemon starting...
2012-09-12 14:00:14,606 DEBUG Daemon started
2012-09-12 14:00:14,607 DEBUG Registering service entries
2012-09-12 14:00:14,608 DEBUG REGISTRATION: Endpoint ID: myriad8.zcu.cz_lbserver_org.glite.lb.Server; URL: https://myriad8.zcu.cz:9003
2012-09-12 14:00:27,564 DEBUG Deleting reqistered entries
2012-09-12 14:00:27,601 ERROR Error during deletion: Bad Request (400): Missing/Invalid query parameter: The delete request must contain a query parameter: /serviceadmin?Service_Endpoint_URL = <SERVICE URL>

@martonivan
Copy link
Contributor

According the new interface definition the DELETE operation needs Service_Endpoint_ID instead of Service_Endpoint_URL, and the last version of emir-serp is prepared for this.

As amemon previously told, the upgrade of zam052v04 EMIR service will start soon to a version that (only) supports/implements this new interface.

The error message in the last line clearly show (for me, who was working on this product ;-) ) that the problem is because this interface version mismatch.

I recommend to wait for the service upgrade. Then you should just restart (or start again) the service.

@amemon
Copy link
Member

amemon commented Feb 25, 2013

This issue should be moved to emir-serp project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants