- RAS-run - RePEc Lists

bdb files deleted
by Thomas Krichel 07 Jan '11

07 Jan '11

We have three corrupt bdbs, I deleted two files. I think the site should now be operationall, but please test drive then set back the DNS. Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel

2 2

Re: [RAS] internal server error
by Thomas Krichel 07 Jan '11

07 Jan '11

Christian Zimmermann writes > I guess they are more impatient for the stats than for the profile > updates. > > That said, I can try to lobby for a new machine in St. Louis before > I get there. My original hope was to move nebka, and then calmly > build a better clone in parallel. That's fine if we add a disk. But again, a cloud based solution will be better. Have them pay $100 a month and we have the box to do what we want. > But it looks like we need to hurry. But I suspect this can still not > be done quickly, in particular because of the reliance on rsync. Are you starting with rsync-is-bad-talk again? Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel

1 0

internal server error
by Christian Zimmermann 07 Jan '11

07 Jan '11

again. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann(a)uconn.edu http://ideas.repec.org/e/pzi1.html

2 9

up and running?
by Christian Zimmermann 07 Jan '11

07 Jan '11

I managed to extract the info I need for the mailing, and managed to change my profile. However, checking on events I get We are sorry. A problem happened inside our system. It is not your fault. Here is what happened: DBD::mysql::st execute failed: Table './acis/events' is marked as crashed and should be repaired at /home/aras/acis/lib/sql_helper.pm line 453. ...propagated at /home/aras/acis/lib/ACIS/Web/Admin/Events.pm line 685. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann(a)uconn.edu http://ideas.repec.org/e/pzi1.html

2 1

the disk is too small
by Thomas Krichel 06 Jan '11

06 Jan '11

aras@nebka:~/acis$ mysql ERROR 1040 (08004): Too many connections This appears to be the issue.... nebka:/var/log/apache2# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 134574084 130663872 0 100% / tmpfs 1558300 0 1558300 0% /lib/init/rw udev 10240 588 9652 6% /dev tmpfs 1558300 4 1558296 1% /dev/shm The disk space is full beacuse I am trying to get a backup copy of mysql. Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel

2 6

Internal Server Error
by Christian Zimmermann 06 Jan '11

06 Jan '11

at http://auhtors.repec.org/ Cannot do anything, have realtors visiting the house today. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann(a)uconn.edu http://ideas.repec.org/e/pzi1.html

1 0

updates
by Christian Zimmermann 06 Jan '11

06 Jan '11

I have received several complaints that new papers and institutions do not make it to RAS after several days. Are these update processes running? Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann(a)uconn.edu http://ideas.repec.org/e/pzi1.html

2 13

Cron <aras@nebka> /usr/bin/db4.6_recover -h ~/acis/RI/data ; /usr/bin/db4.6_checkpoint -1 -h ~/acis/RI/data && /usr/bin/db4.6_archive -d -h ~/acis/RI/data (fwd)
by Christian Zimmermann 06 Jan '11

06 Jan '11

Looks like the issue is with the way the Mysql upgrade was done... Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann(a)uconn.edu http://ideas.repec.org/e/pzi1.html ---------- Forwarded message ---------- Date: Tue, 4 Jan 2011 03:30:48 -0500 From: Cron Daemon <root(a)authors.repec.org> To: "aras(a)authors.repec.org" <aras(a)authors.repec.org> Subject: Cron <aras@nebka> /usr/bin/db4.6_recover -h ~/acis/RI/data ; /usr/bin/db4.6_checkpoint -1 -h ~/acis/RI/data && /usr/bin/db4.6_archive -d -h ~/acis/RI/data db4.6_recover: file unknown has LSN 493110/3893017, past end of log at 493110/3503504 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493110/3893017, past end of log at 493110/3503504 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493110/3893017, past end of log at 493110/3503504 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493110/3893017, past end of log at 493110/3503504 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493110/3893017, past end of log at 493110/3503504 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493110/3893017, past end of log at 493110/3503504 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493110/3893017, past end of log at 493110/3503504 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment db4.6_recover: file unknown has LSN 493110/3893017, past end of log at 493110/3503504 db4.6_recover: Commonly caused by moving a database from one database environment db4.6_recover: to another without clearing the database LSNs, or by removing all of db4.6_recover: the log files from a database environment

2 5

Re: [RAS] wrong author referenced
by Thomas Krichel 04 Jan '11

04 Jan '11

2 1

Re: [RAS] Cron <aras@nebka> /usr/bin/db4.6_recover -h ~/acis/RI/data ; /usr/bin/db4.6_checkpoint -1 -h ~/acis/RI/data && /usr/bin/db4.6_archive -d -h ~/acis/RI/data
by Christian Zimmermann 31 Dec '10

31 Dec '10

What the heck is all that, and how would a reboot help? Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann(a)uconn.edu http://ideas.repec.org/e/pzi1.html On Fri, 31 Dec 2010, Cron Daemon wrote: > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment > db4.6_recover: file unknown has LSN 492969/2475660, past end of log at 492969/1295897 > db4.6_recover: Commonly caused by moving a database from one database environment > db4.6_recover: to another without clearing the database LSNs, or by removing all of > db4.6_recover: the log files from a database environment >

1 0