BAR Website?

Wow - I have been inactive for awhile and was hoping to log on to BAR and see what everyone has been up to, and WHAM - no website. Weird timing. Haven't been on RC for a long, long time but glad I found this thread!
Hope things are running again soon.
-Maureen (Mola mola)
 
Last edited:
I am starting to have withdrawals.....I NEED MY BAR!!!!



I thought Bruce (Centurio) would be the first to crack...

But I agree I feel like there is something tangible missing with the site down for so long.
 
I thought Denzil was going to look into this yesterday. Still nothing? Be nice if one of the officers could give an update.
 
I'm pretty sure denzil hasn't touched it yet.

If someone can just text me all the server details, I'll just go in and mess around with it now. I need SSH access to the servers, and credentials to the databases.
 
I'm pretty sure denzil hasn't touched it yet.

If someone can just text me all the server details, I'll just go in and mess around with it now. I need SSH access to the servers, and credentials to the databases.

I think this is the problem -- Denzil hasn't given anyone else admin privileges or server info. We seem to have no other option which is too bad as there are a number of folks that could handle this.
 
I guess unless your are an officer the is no point in having the credentials.


Sent from my iPhone using Tapatalk Pro
 
Gotta keep the credentials pretty tightly held... just hang tight, it’ll be back. (Hopefully)

Now, which one of you is selling that gem tang?!
 
Either it's an extremely complicated problem, or Denzil is having a hard time finding time to look into it.

Here's what I would try:

1. SSH in and restart the database server (MySQL it looks like)
2. If it doesn't work, seems like there's duplicate keys or entries (syncing problem?). Just delete the duplicate entry/key. You might lose one bit of data, but we're not a bank and we're not going to need it. Another thing is, we could just update the index on it or do something else that can kill the db error.
3. If backups are kept, we can look for the last good backup and restore it into the active database.

All of these things need SSH credentials and database credentials.
 
Either it's an extremely complicated problem, or Denzil is having a hard time finding time to look into it.

Here's what I would try:

1. SSH in and restart the database server (MySQL it looks like)
2. If it doesn't work, seems like there's duplicate keys or entries (syncing problem?). Just delete the duplicate entry/key. You might lose one bit of data, but we're not a bank and we're not going to need it. Another thing is, we could just update the index on it or do something else that can kill the db error.
3. If backups are kept, we can look for the last good backup and restore it into the active database.

All of these things need SSH credentials and database credentials.



Or just simply have host support look into the problem.


Sent from my iPhone using Tapatalk Pro
 
Back
Top