Thread: Problem installing Postgresql 8 on Win 2000
Hello All
I am trying to use the pginstaller to install on a Win2000 machine. I do have NOD32 installed but as I notice in the FAQ there might be problems I have disabled it. I am running the install with all default options and my install fails when initdb tries to run. I get a PostgreSQL 8.0 popup box.
Failed to run initdb: 1!
Please see the logfile in 'C:\Program Files\PostgreSQL\8.0\tmp\initdb.log'
That logfile gets down to
creating template1 database in C:/Program files/PostgreSQL/8.0/data/base/1 ... Bad command or file name
could not write to child process: Invalid argument
initdb: removing contents of data directory "C:/Program Files/PostgreSQL/8.0/data"
I tried when beta 1 first came out to install PostgreSQL on a Win2000 computer and got similar errors and could never get to the bottom of the problem. I now need to get PostgreSQL working to support a customers application so am prepared to put a lot more time into debugging if anyone out there can help.
Regards
Richard
_______________________________________
Richard Luckhurst
Manager / Engineer
Sound Advice / BSP Internet Services
P.O. Box 104
Narrabri NSW 2390
Phone 02 6792 6060
Fax 02 6792 6161
http://www.soundadvice.aunz.net
http://www.bsp.aunz.com
> Hello All > > I am trying to use the pginstaller to install on a Win2000 > machine. I do have NOD32 installed but as I notice in the FAQ > there might be problems I have disabled it. I am running the > install with all default options and my install fails when > initdb tries to run. I get a PostgreSQL 8.0 popup box. Please try to uninstall it. Disabling it often leaves some parts running. And AV is a very common cause for this kind of errors. > Failed to run initdb: 1! > Please see the logfile in 'C:\Program > Files\PostgreSQL\8.0\tmp\initdb.log' > > That logfile gets down to > > creating template1 database in C:/Program > files/PostgreSQL/8.0/data/base/1 ... Bad command or file name > could not write to child process: Invalid argument > initdb: removing contents of data directory "C:/Program > Files/PostgreSQL/8.0/data" > > I tried when beta 1 first came out to install PostgreSQL on a > Win2000 computer and got similar errors and could never get > to the bottom of the problem. I now need to get PostgreSQL > working to support a customers application so am prepared to > put a lot more time into debugging if anyone out there can help. If you install without initdbing, can you then run initdb manually? (try the above with uninstalling AV first, though..) //Magnus
Hello Magnus Does this mean that the NOD32 Anti Virus would need to be removed to allow PostgreSQL to run or just to allow the installer to complete? It is not an option to remove NOD32 for good though the customer will allow its removal to test this installation. Could you please explain the procedure for installing without initdbing? And then running initdb manually. Thanks Richard -----Original Message----- From: Magnus Hagander [mailto:mha@sollentuna.net] Sent: Wednesday, 3 August 2005 5:28 PM To: Richard Luckhurst; PGSQL Hackers Subject: RE: [pgsql-hackers-win32] Problem installing Postgresql 8 on Win 2000 > Hello All > > I am trying to use the pginstaller to install on a Win2000 > machine. I do have NOD32 installed but as I notice in the FAQ > there might be problems I have disabled it. I am running the > install with all default options and my install fails when > initdb tries to run. I get a PostgreSQL 8.0 popup box. Please try to uninstall it. Disabling it often leaves some parts running. And AV is a very common cause for this kind of errors. > Failed to run initdb: 1! > Please see the logfile in 'C:\Program > Files\PostgreSQL\8.0\tmp\initdb.log' > > That logfile gets down to > > creating template1 database in C:/Program > files/PostgreSQL/8.0/data/base/1 ... Bad command or file name > could not write to child process: Invalid argument > initdb: removing contents of data directory "C:/Program > Files/PostgreSQL/8.0/data" > > I tried when beta 1 first came out to install PostgreSQL on a > Win2000 computer and got similar errors and could never get > to the bottom of the problem. I now need to get PostgreSQL > working to support a customers application so am prepared to > put a lot more time into debugging if anyone out there can help. If you install without initdbing, can you then run initdb manually? (try the above with uninstalling AV first, though..) //Magnus __________ NOD32 1.1185 (20050801) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com
> Hello Magnus > > Does this mean that the NOD32 Anti Virus would need to be > removed to allow PostgreSQL to run or just to allow the > installer to complete? It is not an option to remove NOD32 > for good though the customer will allow its removal to test > this installation. It may be needed. I've seen I think one case where just the installer required it, I've seen others where it simply did not work at all, and required complete removal. In some cases, it's enough to remove parts of the AV (if it has a personal firewall, get rid of that first..). In other cases, upgrading or downgrading to a different version may help. But it's worth a try to remove it just for the installation. > Could you please explain the procedure for installing without > initdbing? And then running initdb manually. During install, there is a screen about initializing the database. Uncheck the box so it doesn't run this step. This will install just the files and the service (which will not work until you have manually run initdb). Then run the following on a commandline (adjust for paths, account names, encoding and locale of course): runas /user:%COMPUTERNAME%\postgres cmd.exe --> enter *service account password* This will give you a new commandshell running as the service account. In this window, run: cd "c:\program files\postgresql\8.0.3\bin" initdb -W -A md5 -D ..\data -E LATIN1 --locale=Swedish_Sweden.1252 --> on the prompt, enter the password for the *database superuser* This should initialize the database in the data directory. If you don't get an error here, you shuold now be able to start the service. //Magnus