Dale,

Yes I know this tool, thanks. Actually I ran it last night and found a rather large number of Strings while garbage collection is reporting 0 dead objects.  So my next step was trying to see if I have a bug somewhere and if I am holding to some un-needed objects. 

BTW, the scanbackup tool does not seem to work with the backups generated from GemTools.  It fails at LogRecordHdr > isBackupDataRecord

"LOG_BACKUP_DATA_RECORD defined in logdisk.ht" (CompatibilityLevel = 830 and: [self recordKind = 17]) ifTrue: [^true]. ^false.

the recordKind is was not 17 (sorry I forgot to write the number down, I think it was 19).

It worked if I execute the fullBackup from topaz.

Thierry

James,

I still have the backup and I just tried again to scan it but it failed at the same place.

In fact it fails reading the 'firstPhyicalRecord' (see attachment).

If I inspect the header (LogRecordHdr), I see: 

ByteArray withAll: #(0 0 0 0 0 0 0 0 0 0 19 0 152 62 0 0 )

You can see the value 19 instead of the expected 17 (in isBackupDataRecord).  My backup file is too large to send, but here is a screen copy of the hex representation of the file start. The 19 (h13) is highlighted.

Thierry

<Screen Shot 2012-02-09 at 2.20.49 PM.png><Screen Shot 2012-02-09 at 2.30.04 PM.png>

Hello,

  After a long series of calls and answers in Seaside, I got an Object does not exist error that brought down the fast cgi gateway. My production error handler was not triggered, although it was installed, as far as I could tell. Strange. My supervise fastcgi process also did not pick up my dead fastcgi process. Not a good day.

Object does not exist errors

Workaround:

none/not applicable

Am 09.02.2012 um 22:41 schrieb Lawrence Kellogg:

Hello,

This is not specifically a Gemstone/Seaside query but I'll throw it out there anyway.

I have a domain which I have used a CNAME record to point to my Amazon EC2

instance running Seaside. The www version of my domain works great.

Now, if I try just the non-www version of my domain, I get forwarded to an "It Works"

page from an Apache server. I had played with Apache but didn't think it was running

now and I don't see an Apache process when I do ps -A.

I talked to the Register.com guys and they said I had to own an A record

to point and that for $50 a year, they would point the non-www address but it didn't work.

Is there some sort of configuration setting on the Amazon side? Is it an NGINX setting?

What do I have to do in order to get the non-www name to point to the www. name.

Larry,

you won't get it made without extra effort I guess. Basically a CNAME is the right thing to do. It is exact the case it was designed for which is a well-misunderstood fact. Unfortunately CNAME does not work on zones itself (the non www name). That is a shortcoming of DNS. On the other hand a CNAME would introduce problems when you reboot a machine. It will take up to 3 hours to have your CNAME point to the right address. Just look yourself

dig soa compute-1.amazonaws.com +short

pdns1.ultradns.net. hostmaster.amazon.com. 2011110102 10800 3600 2592000 60

The number 10800 is the zone TTL meaning the number of seconds it should be cached. So for two reasons the CNAME does not seem what you are looking for. Amazon offers Route 53 DNS service where you could shorten the TTL. But that wouldn't solve the access for your domain ip. The easiest will be to buy an elastic IP or if you have a big installation an elastic load balancer. Then you just need to make nginx aware that there are www. and none www names it should react upon (you can just write the server names separated by space in the server name line.
I don't know what is causing the "It works". But the "It works" is just a html file. Probably nginx points to the same document root as an apache installation. Usually to be found in /var/www/

 # nginx -t -c /etc/nginx/nginx.conf 

 2007/10/18 20:55:07 [info] 3125#0: the configuration file /etc/nginx/nginx.conf syntax is ok
 2007/10/18 20:55:07 [info] 3125#0: the configuration file /etc/nginx/nginx.conf was tested successfully

 # ps -ef|grep nginx
 root      1911     1  0 18:00 ?        00:00:00 nginx: master process /usr/sbin/nginx
 www-data  1912  1911  0 18:00 ?        00:00:00 nginx: worker process

 # kill -HUP 1911

Well...this is not an advize to do it but there is one option you can do if saving money is your top priority. You can use an dyndns provider to serve your domain. There are ready made scripts that are triggered when your machine is booted. The script reads the assigned IP address and updates the entry at your dyndns provider. The TTL for dyndns domains is usually 60 seconds. That could solve your troubles. But then you would need your domain to reside at the dyndns provider. Otherwise there is less chance to update the IP address for your non-www name. And maybe there are also costs involved

hope this helps,

Norbert