Skip to content
This repository has been archived by the owner on Nov 13, 2023. It is now read-only.

View last error log returns 'Invalid error log index' #23

Open
ghost opened this issue Apr 2, 2010 · 5 comments
Open

View last error log returns 'Invalid error log index' #23

ghost opened this issue Apr 2, 2010 · 5 comments

Comments

@ghost
Copy link

ghost commented Apr 2, 2010

When clicking on the button [View last error log from requisitioned server] in the account page, the following error is returned:

Invalid error log index

This happens at both syntensity.com and my own master server. It's likely because no error was recorded, but it seemed to always return this (even when there appeared to be an error with the instance, but it was with requisitioning not necessarily in the running of the server). A little more explanation of what this button does (for end users) will probably be helpful, perhaps a link to the relevant wiki entry?

@kripken
Copy link
Owner

kripken commented Apr 5, 2010

A first check shows this works for me.

Got a set of actions that can reliably reproduce this?

@ghost
Copy link
Author

ghost commented Apr 5, 2010

Can you log into syntensity.com as another user? If so, log in as me and hit the button.

@kripken
Copy link
Owner

kripken commented Apr 5, 2010

I can't without your password.

But anyhow that error is correct behavior if there is no error log to display (text could be nicer I guess...) So one would also need to crash a server (and wait for it to restart and upload the error log). Also, this must be a server that uploads crash logs (like the syntensity.com ones are, but if you run your own, by default they won't).

@ghost
Copy link
Author

ghost commented Apr 5, 2010

Right, sorry if the original ticket wasn't clear but this is what I assumed was happening.

The reason this looked like an error is because it is not served within the syntensity.com site template. I think to others it will look like an error has occurred on the site, but it's not a big deal. Feel free to close the ticket if you don't think it's worth keeping open.

@kripken
Copy link
Owner

kripken commented Apr 5, 2010

Ah, ok.

Well, it should be clearer, I'll keep the issue open to remember to make the text nicer at some point.

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

No branches or pull requests

1 participant