Skip site navigation (1) Skip section navigation (2)

Re: Sporadic ValidateBinary error

From: s0lao(at)netscape(dot)net (S(dot) L(dot))
To: robin(dot)wynn(at)ngc(dot)com ("Wynn, Robin"), pgsql-cygwin(at)postgresql(dot)org
Subject: Re: Sporadic ValidateBinary error
Date: 2005-07-17 16:42:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-cygwin
>2005-07-14 21:03:33 [2176] DEBUG: ValidateBinary:
>"/jms_root/bin/postmaster" is not other read/execute
>The last line caught my attention, but as I said, it's the same machine,
>with the same postmaster executable, with the same permissions.  The
>user in both cases starting Postgres is SYSTEM, and SYSTEM has full
>control of the executable.  The sporadic nature of the problem makes me
>wonder if there is some sort of race condition, but I can't think of
>anything that would be touching the postmaster executable besides our
>startup script.  Does this ring any bells with anyone? 

The first bell it rang was that a disk issue condition could happen. A chkdsk on the posmaster in your scripts might help.

Also in that debug line, I think the key word is "other". It doesn't matter SYSTEM is "rwx" on the postmaster, but you must make sure other (the righmost rights) is at least "r-x" (as ValidateBinary suggests). So a "chmod <put_proper_options> postmaster" in your scripts, could also be a good ideea.


Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at

pgsql-cygwin by date

Next:From: Frank-Michael MoserDate: 2005-07-19 10:12:40
Subject: Re: postmaster startup segfault: STATUS_ACCESS_VIOLATION at eip=610028AA
Previous:From: Wynn, RobinDate: 2005-07-15 12:59:56
Subject: Sporadic ValidateBinary error

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group