Re: [BUGS] BUG #5677: missing libuuid.so.16 library
Hi Andrew, I have fixed this issue. Thanks for reporting. Regards, Dharmendra On Sat, Sep 25, 2010 at 8:10 AM, Andrew Geery wrote: > > The following bug has been logged online: > > Bug reference: 5677 > Logged by: Andrew Geery > Email address: andrew.ge...@gmail.com > PostgreSQL version: 9.0 > Operating system: Ubuntu 10.10 > Description:missing libuuid.so.16 library > Details: > > In 8.4, the one-click installer for Linux from EDB included the libuuid.so* > libraries in the PGLIB directory. However, in the 9.0 one-click installer > for Linux from EDB, these libraries are no longer included. On Ubuntu > 10.10, attempting to run the uuid-ossp.sql script produces this error > because of the missing libuuid* libraries: > > ERROR: could not load library > "/opt/PostgreSQL/9.0/lib/postgresql/uuid-ossp.so": libuuid.so.16: cannot > open shared object file: No such file or directory > SQL state: 58P01 > > The workaround is to copy the libuuid* libraries from the 8.4 installation > into the 9.0 PGLIB directory. > > Not sure why those libraries were removed in 9.0 -- I was unable to find an > Ubuntu package that supplied libuuid.so.16. In /lib, there are > libuuid.so.1 > and libuuid.so.1.3.0, but symbolically linking them to libuuid.so.16 > failed. > > Thanks > Andrew > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs > -- Dharmendra Goyal Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91-20-30589493 Mobile: +91-9552103323 Website: http://www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Re: [BUGS] BUG #5686: Problem connecting to server
Hi, Can you please send 8.4 installation log which can be found inside %TEMP%. Thanks, Dharmendra On Thu, Sep 30, 2010 at 7:00 AM, Maly Lemire wrote: > > The following bug has been logged online: > > Bug reference: 5686 > Logged by: Maly Lemire > Email address: maly.lem...@gmail.com > PostgreSQL version: 8.4.4-1 > Operating system: Windows XP > Description:Problem connecting to server > Details: > > If I install postgresql-8.4.4-1 on a computer where no previous > installation > of protsgre have been made, I get a connection failed error when I log in > with PGAdminIII. > > If I install postgresql-8.3.8-1 on the same computer, it works ok. Then if > I > desinstall postgresql-8.3.8-1, and install postgresql-8.4.4-1, there is no > connection error anymore. > > I've tried deleting postgres user, deleting progres files in program files > and reinstalling still no connection error. > > I would like to be sure I could install 8.4.4-1 on a cumputer with windows > XP and that as no previous installation of postgre. > > Thanks, > Maly Lemire > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs > -- Dharmendra Goyal Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91-20-30589493 Mobile: +91-9552103323 Website: http://www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Re: [BUGS] BUG #5696: cannot upgrade to 9.0.1
Hi Dave, We do not allow 64 bit installer to run on 32 bit windows and this check is already there. Regards, Dharmendra On Thu, Oct 7, 2010 at 5:13 PM, Dave Page wrote: > On Thu, Oct 7, 2010 at 12:40 PM, Tony Marston > wrote: > > I found the log file, and when it looked at it there was a reference to > the > > 64 bit version of Windows, which I don't have. I downloaded the 32 bit > > version (which I'm sure I did the first time, but I must have been > wrong), > > ran it, and it worked OK. Sorry for the confusion. > > OK, thanks for letting us know. > > Dharmendra - can you see if there's an easy way to prevent the 64bit > installer running on 32bit Windows please? > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise Postgres Company > -- Dharmendra Goyal Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91-20-30589493 Mobile: +91-9552103323 Website: http://www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Re: [BUGS] How do I remove PostgreSQL completely?
Hi, How did you install existing instance of PG server..?? Did you use any of the community installers..?? IMO to avoid data load, you need to remove your data directory if it is not required now. To get rid of user accounts, you need to remove them as well. Regards, On Mon, Oct 18, 2010 at 7:40 PM, Sebastian Frey wrote: > Hi guys! > > I wanted to install PokerTracker3, but the required PostgreSQL could not be > installed because (apparently) it was installed before by another program... > So, when I start PokerTracker3, a PostgreSQL server window opens containing > already filled in data about Server, Password etc... > When I press connect, the window "PostgreSQL wasn't able to connect to this > database. Please check configuration (or something like this)" appears. > > So I searched on the internet and found on one of the many support websites > the instruction to unistall PostgreSQL, which I did, but apparently the > account wasn't fully deleted, so the problem is still there and I have no > idea of how to get rid of it! > > I would greatly appreciate your help, but I need very basic instructions > since I have only very basic knowledge of computers in general... > > Best, sebastian > ___ > Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! > Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02 > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs > -- Dharmendra Goyal Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91-20-30589493 Mobile: +91-9552103323 Website: http://www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Re: [BUGS] BUG
Hi Alexia, This issue have been fixed for all the platforms. Can you please send output of "ls -l install_dir/*lib/postgresql" for more information.* * * *Thanks,* *Dharmendra * On Sat, Oct 23, 2010 at 7:39 AM, Alexia Lau wrote: > Hi Dharmendra, > > > > I am encountering the same exact problem with the 9.0 one-click installer > for Linux from EnterpriseDB on SUSE 11 and RedHat 5.5 with the latest > release this week. In your email dated 9/28/10, you indicated it’s fixed. > Will you fix it for SUSE 11 and RedHat 5.5? > > > > Sincerely, > > Alexia > > > ------ > > > > > > *Author: *Dharmendra Goyal > *Date: * 2010-09-28 02:36 -700 > *To: *Andrew Geery > *CC: *pgsql-bugs > *Subject: *Re: [BUGS] BUG #5677: missing libuuid.so.16 library > > Hi Andrew, > > I have fixed this issue. Thanks for reporting. > > Regards, > Dharmendra > > On Sat, Sep 25, 2010 at 8:10 AM, Andrew Geery wrote: > * > > > > The following bug has been logged online: > > > > Bug reference: 5677 > > Logged by: Andrew Geery > > Email address: andrew.ge...@??? > > PostgreSQL version: 9.0 > > Operating system: Ubuntu 10.10 > > Description: missing libuuid.so.16 library > > Details: > > > > In 8.4, the one-click installer for Linux from EDB included the > libuuid.so* > > libraries in the PGLIB directory. However, in the 9.0 one-click installer > > > for Linux from EDB, these libraries are no longer included. On Ubuntu > > 10.10, attempting to run the uuid-ossp.sql script produces this error > > because of the missing libuuid* libraries: > > > > ERROR: could not load library > > "/opt/PostgreSQL/9.0/lib/postgresql/uuid-ossp.so": libuuid.so.16: cannot > > open shared object file: No such file or directory > > SQL state: 58P01 > > > > The workaround is to copy the libuuid* libraries from the 8.4 > installation > > into the 9.0 PGLIB directory. > > > > Not sure why those libraries were removed in 9.0 -- I was unable to find > an > > Ubuntu package that supplied libuuid.so.16. In /lib, there are > > libuuid.so.1 > > and libuuid.so.1.3.0, but symbolically linking them to libuuid.so.16 > > failed. > > > > Thanks > > Andrew > > > > -- > > Sent via pgsql-bugs mailing list (pgsql-b...@???) > > To make changes to your subscription: > > http://www.postgresql.org/mailpref/pgsql-bugs > >* > > > -- > > Dharmendra Goyal > > Senior Software Engineer > > EnterpriseDB Corporation > > The Enterprise Postgres Company > > > > Phone: +91-20-30589493 > Mobile: +91-9552103323 > > Website: http://www.enterprisedb.com > EnterpriseDB Blog: http://blogs.enterprisedb.com/ > Follow us on Twitter: http://www.twitter.com/enterprisedb > > This e-mail message (and any attachment) is intended for the use of the > individual or entity to whom it is addressed. This message contains > information from EnterpriseDB Corporation that may be privileged, > confidential, or exempt from disclosure under applicable law. If you are > not > the intended recipient or authorized to receive this for the intended > recipient, any use, dissemination, distribution, retention, archiving, or > copying of this communication is strictly prohibited. If you have received > this e-mail in error, please notify the sender immediately by reply e-mail > and delete this message. > > > -- Dharmendra Goyal Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91-20-30589493 Mobile: +91-9552103323 Website: http://www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Re: [BUGS] BUG
Hi Alex, I saw related checkins. This issue was actually fixed on 4th October, the day on which 9.0.1 was released and 9.0.1 build missed this issue. If you want a work around then please take required uuid library from 8.4 installation. Please let me know if you still have any issue related to this. Regards, Dharmendra On Mon, Oct 25, 2010 at 11:19 PM, Alexia Lau wrote: > Hi Dharmendra, > > > > Thanks for responding back. Attached are the output lists from SUSE 11 > 32-bit, SUSE 11 64-bit, RedHat 5.5 32-bit, and RedHat 64-bit. I used the > EnterpriseDB one-click installers for Linux 32-bit and 64-bit listed below > from http://www.enterprisedb.com/products/download.do. Is the fix suppose > to be reflected in the one-click installers for Linux dated October 4, 2010 > from EnterpriseDB? If not, where would I find the fix? Let me know if you > need any additional information. > > > > · postgresql-9.0.1-1-linux.bin > > · postgresql-9.0.1-1-linux-x64.bin > > > > Regards, > > Alexia > > > > *From:* Dharmendra Goyal [mailto:dharmendra.go...@enterprisedb.com] > *Sent:* Sunday, October 24, 2010 10:04 PM > *To:* Alexia Lau > *Cc:* PostgreSQL Bugs > *Subject:* Re: [BUGS] BUG > > > > Hi Alexia, > > > > This issue have been fixed for all the platforms. Can you please send > output of "ls -l install_dir/*lib/postgresql" for more information.* > > > > *Thanks,* > > *Dharmendra* > > On Sat, Oct 23, 2010 at 7:39 AM, Alexia Lau wrote: > > Hi Dharmendra, > > > > I am encountering the same exact problem with the 9.0 one-click installer > for Linux from EnterpriseDB on SUSE 11 and RedHat 5.5 with the latest > release this week. In your email dated 9/28/10, you indicated it’s fixed. > Will you fix it for SUSE 11 and RedHat 5.5? > > > > Sincerely, > > Alexia > > > -- > > > > > > *Author: *Dharmendra Goyal > *Date: * 2010-09-28 02:36 -700 > *To: *Andrew Geery > *CC: *pgsql-bugs > *Subject: *Re: [BUGS] BUG #5677: missing libuuid.so.16 library > > Hi Andrew, > > I have fixed this issue. Thanks for reporting. > > Regards, > Dharmendra > > On Sat, Sep 25, 2010 at 8:10 AM, Andrew Geery wrote: > * > > > > The following bug has been logged online: > > > > Bug reference: 5677 > > Logged by: Andrew Geery > > Email address: andrew.ge...@??? > > PostgreSQL version: 9.0 > > Operating system: Ubuntu 10.10 > > Description: missing libuuid.so.16 library > > Details: > > > > In 8.4, the one-click installer for Linux from EDB included the > libuuid.so* > > libraries in the PGLIB directory. However, in the 9.0 one-click installer > > > for Linux from EDB, these libraries are no longer included. On Ubuntu > > 10.10, attempting to run the uuid-ossp.sql script produces this error > > because of the missing libuuid* libraries: > > > > ERROR: could not load library > > "/opt/PostgreSQL/9.0/lib/postgresql/uuid-ossp.so": libuuid.so.16: cannot > > open shared object file: No such file or directory > > SQL state: 58P01 > > > > The workaround is to copy the libuuid* libraries from the 8.4 > installation > > into the 9.0 PGLIB directory. > > > > Not sure why those libraries were removed in 9.0 -- I was unable to find > an > > Ubuntu package that supplied libuuid.so.16. In /lib, there are > > libuuid.so.1 > > and libuuid.so.1.3.0, but symbolically linking them to libuuid.so.16 > > failed. > > > > Thanks > > Andrew > > > > -- > > Sent via pgsql-bugs mailing list (pgsql-b...@???) > > To make changes to your subscription: > > http://www.postgresql.org/mailpref/pgsql-bugs > >* > > -- > > Dharmendra Goyal > > Senior Software Engineer > > EnterpriseDB Corporation > > The Enterprise Postgres Company > > > > Phone: +91-20-30589493 > Mobile: +91-9552103323 > > Website: http://www.enterprisedb.com > EnterpriseDB Blog: http://blogs.enterprisedb.com/ > Follow us on Twitter: http://www.twitter.com/enterprisedb > > This e-mail message (and any attachment) is intended for the use of the > individual or entity to whom it is addressed. This message contains > information from EnterpriseDB Corporation that may be privileged, > confidential, or exempt from disclosure under applicable law. If you are > not > the intended recipient or authorized to receive this for the intended > recipient, any use, dissemination, distribution, retention, archiving, or > copying of this communication is strictly prohibited. If you hav
Re: [BUGS] BUG #5807: psql fails to launch with "Cannot read termcap database; using dumb terminal settings. Aborted"
If you install libtermcap then it will start working good. We have tested it at our end. On Fri, Jan 7, 2011 at 2:24 AM, Gabe Nell wrote: >> There was a change in 9.0.2 to use libedit instead of readline for >> this (readline is GPL, which is not acceptable to some people who wish >> to use Postgres in other products). One of my colleagues has tested >> the issue reported and confirmed that installing the OS's termcap >> package should solve the problem. > > Ubuntu doesn't seem to use termcap, an apt-cache search for termcap > turns up nothing relevant. I did some searching and the closest > suggestion I could find was to install libncurses5-dev, but this > didn't help. Can you suggest that the appropriate package to install > on Ubuntu? > > Thanks! > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs > -- Dharmendra Goyal Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91-20-30589493 Mobile: +91-9552103323 Website: http://www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Windows x86-64 One-Click Install (9.1.2-1, 9.0.6-1) hangs on "initialising the database cluster" (with work-around)
Installer works at our end without any issue. I remember we had considered using "%COMSPEC% /c" earlier but dropped it because command windows opens up for every new file execution. On Fri, Jan 27, 2012 at 3:40 PM, Dave Page wrote: > iirc, using %COMSPEC% /c will cause the scripts to run in a visible > command window, which is pretty ugly, and doesn't seem to be necessary > anywhere except on your machine! > > What's the output from the "set" command on that box? > > On Thu, Jan 26, 2012 at 6:54 PM, Eric Borts wrote: > > Also, here is a link to the same issue on StackOverflow: > > > http://stackoverflow.com/questions/3559719/wscript-shell-run-doesnt-work-consistently > > > > Also solved using %COMSPEC% /c, though it doesn't say why this is a > problem. > > > > Cheers, > > Eric > > > > > > On 1/26/2012 11:37 AM, Eric Borts wrote: > > > > On 1/26/2012 1:17 AM, Dave Page wrote: > > > > Dharmendra, can you look into this please? > > > > Eric, is there anything unusual about the configuration of your > > machine? Suffice it to say, this doesn't normally happen. > > > > Hi Dave, I'm guessing the answer to that question is "yes". The machine > came > > preinstalled with Norton Internet Security, but this was turned off when > I > > ran the install. After further investigation to the .bat file, I realized > > that I am also missing the "Edit" option when I right click a batch file. > > > > I investigated, uninstalled stuff, disabled a lot of stuff in my > registry, > > and nearly bricked my computer. After three hours, I'm going to have to > ask > > for suggestions. Here's what I found/tried: > > > > 1. uninstalled Norton Internet Security (and rebooted) > > 2. uninstalled Acrobat Reader > > 3. disabled all ContextMenuHandlers by > > a. renaming HKCR/*/shellex to oldshellex > > b. renaming HKCR/AllFileSystemsObjects/shellex to oldshellex > > c. tried, but was unable to rename HKCR/batfile/ShellEx, so renamed > > HKCR/batfile/ShellEx/ContextMenuHandlers to oldContextMenuHandlers > > 4. disabled all non-Microsoft shell extensions using ShellExView > > 5. rebooted - computer bricked (black screen when Windows should be > loading) > > 6. booted in safe mode > > 7. tested script (from my original response) and right click. > > a. no Edit option in batch file context menu > > b. script hung as before > > 8. Undid steps 3 and 4 in safe mode > > 9. Rebooted - booted into windows properly > > 10. Still no Edit in context menu and script still hangs > > > > I'm open to suggestions. I think it might be related to Edit menu missing > > from my batch file, as this is the only odd thing that I can tell about > my > > machine. I have another similar machine (earlier model Vaio) that both > has > > the Edit menu and runs the test script successfully. I compared the > > HKCR/batfile registry trees (using TortoiseSVN diff) and they are > identical. > > Short of comparing the entire registry I'm at a loss. > > > > Would it be too dangerous to use WScript.Shell.Exec or to use > > WScript.Shell.Run "%COMPSEC% /c" ? This has been an 11 hour struggle for > me > > so far, and I know at least a few others have had this same problem. > Here is > > a link to my work around on enterprisedb. > > > > Thanks, > > Eric > > > > Reference Links: > > > http://www.pcreview.co.uk/forums/edit-print-open-missing-shell-context-menu-cmd-and-bat-files-t2551124.html > > http://windowsxp.mvps.org/slowrightclick.htm > > http://www.nirsoft.net/utils/shexview.html > > > > > > > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > -- Dharmendra Goyal Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91-20-30589493 Mobile: +91-9552103323 Website: http://www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Re: [BUGS] Windows x86-64 One-Click Install (9.1.2-1, 9.0.6-1) hangs on "initialising the database cluster" (with work-around)
On Sat, Jan 28, 2012 at 2:17 AM, Eric Borts wrote: > The installation now runs successfully after deleting that registry key. > > In addition, I tried changing the default action on batch files from > "Open" to "Edit" using the registry (Windows 7). Double-clicking a file > opens it in Notepad, but the installation runs successfully. So it looks > like the UserChoice registry key, however it got there, is the essence of > the problem. > > Which, of course, %COMSPEC% /c would avoid because the program handling > batch files is explicit. > Nice analysis Eric. ANy idea why (which program set this) this particular registry was set. Dave, shall we consider using "%COMSPEC% /c" with 0 as second parameter..?? > > Thanks, > Eric > > > On 1/27/2012 1:16 PM, Eric Borts wrote: > > I found the problem with my computer > here<http://help.lockergnome.com/windows/BAT-File-Association-Broken--ftopict514456.html>. > It turns out this registry entry was causing my problem: > > HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.bat > \UserChoice > Progid REG_SZ (Applications\cmd.exe) > > Deleting the \UserChoice key restored my context menu and ability to run a > ".bat" directly instead of using %COMSPEC%. > > I am going to un-install an re-install postgres to verify that this solves > my installation issues. > > Eric > > > > > > > > On 1/27/2012 12:41 PM, Eric Borts wrote: > > Regarding my final point: > > "Similarly, you may prefer to have the default action for a batch file > (.bat) changed to Edit instead of Open. Double-clicking the file will not > run the commands in the file, and if users want to run the file, they can > use the *Open* command on the shortcut menu." > http://support.microsoft.com/kb/320036 > > This advice would be likely to hang the PostgreSQL installer. > > Cheers, > Eric > > > On 1/27/2012 12:32 PM, Eric Borts wrote: > > Hi Dave and Dharmendra, > > It is not the "%COMSPEC% /c" call that causes the window to popup, but the > WindowStyle parameter to WShell.Run (see Table 3.9 in MS TechNet WSH > Objects / Running > Programs<http://technet.microsoft.com/en-us/library/ee156605.aspx>). > Setting WindowStyle to "0" creates a hidden window. This is how the code in > the installer is currently written. Setting it to "1" creates a visible > window. This happens when using "%COMSPEC% /c" or when calling the batch > file directly. > > Here is a another site > recommending<http://classicasp.aspfaq.com/general/how-do-i-execute-a-dos-command/batch-file/exe-from-asp.html>the > use of "%COMSPEC% /c" with a "0" second parameter, along with a note > about the window (in)visibility: > > "[...] do not run any command that raises a prompt, dialog, msgbox or > any other GUI. This [...] could hang your entire system (since the > invisible GUI will be waiting for a reply [...]" > > Test code is attached that demonstrates using COMSPEC with a "0" versus a > "1". > > Output from SET command is also attached. Note that I've verified that > this problem still occurs in Safe Mode. > > Any other suggestions? I've also posted to > StackOverflow<http://stackoverflow.com/questions/9038927/vbscript-hangs-when-launching-batch-file-with-wshell-script-run>for > adivce. > > A separate line of reasoning for using COMSPEC is that the calling of the > .bat directly assumes that default action is to execute the batch file. If > a user has modified their default .bat actions (which I have not), the > postgres installer will fail. Using COMSPEC will avoid that pitfall. > > I'll keep you posted if I discover why my machine doesn't execute batch > files by default, or how it ended up in this condition. The computer is > only about 2 months old, so I haven't had *that* much time to overwhelm it > with installs. > > Eric > > > > > -- Dharmendra Goyal Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91-20-30589493 Mobile: +91-9552103323 Website: http://www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Re: [BUGS] BUG #6404: postgres account not created during unattended install
On Sat, Jan 21, 2012 at 3:01 AM, wrote: > The following bug has been logged on the website: > > Bug reference: 6404 > Logged by: Mark Phillips > Email address: mark.phill...@mophilly.com > PostgreSQL version: 9.1.2 > Operating system: Mac OS X 10.7 > Description: > > for a stand alone app that uses postgres, the app installer invokes the > shell script installbuilder.sh for the "unattended" install of postgres. > > The pg installer creates a user "PostgreSQL" that is not hidden, but does > not create a hidden account "postgres". As a result, the invocation of > pg_ctl fails. Error is "unknown login: postgres". > pg installer creates "postgres" user which somehow seems to be failing at your machine. Can you please send installation log which can be found under /tmp/install-postgresql.log. Also if you can run installation_path/installer/server/createuser.sh script manually and check the output, it can be helpful. Thanks, -- Dharmendra Goyal Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91-20-30589493 Mobile: +91-9552103323 Website: http://www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Re: [BUGS] BUG #6404: postgres account not created during unattended install
Hi Mark,
Install log shows that your db installation is successful. The error which
you had sent is coming because your earlier installation failed to create
'postgres' user and when you ran the installer again, installer read
/etc/postgres-reg.ini file to check any previous installation and found
that previous installation was done. Hence installer tries to stop the db
server in case it is running using postgres user. This command fails as
postgres user was not created in your first installation because of some
reason. But in latest installation (for which you have sent the log),
postgres user has been created successfully and installation went
successfully. You need to check why postgres user was not created in first
go by checking logs of that installation.
You are checking return status of the installbuilder.sh command run which
is not 0 hence you are getting error ("install of DBMS failed".) in your
script. Can yu please check what is the return value in your script of
installbuilder.sh.
Regards,
On Tue, Jan 31, 2012 at 5:37 AM, Mark Phillips
wrote:
>
> On Jan 29, 2012, at 11:07 PM, Dharmendra Goyal wrote:
>
> On Sat, Jan 21, 2012 at 3:01 AM, wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 6404
>> Logged by: Mark Phillips
>> Email address: mark.phill...@mophilly.com
>> PostgreSQL version: 9.1.2
>> Operating system: Mac OS X 10.7
>> Description:
>>
>> for a stand alone app that uses postgres, the app installer invokes the
>> shell script installbuilder.sh for the "unattended" install of postgres.
>>
>> The pg installer creates a user "PostgreSQL" that is not hidden, but does
>> not create a hidden account "postgres". As a result, the invocation of
>> pg_ctl fails. Error is "unknown login: postgres".
>>
> pg installer creates "postgres" user which somehow seems to be failing at
> your machine. Can you please send installation log which can be found under
> /tmp/install-postgresql.log. Also if you can run
> installation_path/installer/server/createuser.sh script manually and check
> the output, it can be helpful.
>
> Thanks,
> --
> Dharmendra Goyal
>
>
> Thank you for the reply. I apologize for the delay in responding.
>
> File install-postgresql.log attached.
>
> Please review the link below to a post in the postgresql forum for a bit
> more detail about this issue:
>
> http://forums.enterprisedb.com/posts/list/3042.page
>
> I looked into running the createuser.sh script. However, I encountered a
> bit of new information before I could get that far so I include it here in
> case it is relevant.
>
> Beginning anew with a clean os install, I ran the app installer that
> invokes the postgresql installer.
>
> Here is a snippet of the installer script that relates to installing
> postgres:
>
> # adjust current settings to allow the install to execute properly
> log "adjust current shared memory settings"
> log "..refer to
> http://www.postgresql.org/docs/9.1/interactive/kernel-resources.html#SYSVIPC
> "
> sysctl -w kern.sysv.shmmax=1610612736
> sysctl -w kern.sysv.shmall=393216
> sysctl -w kern.sysv.shmmin=1
> sysctl -w kern.sysv.shmmni=32
> sysctl -w kern.sysv.shmseg=8
> sysctl -w kern.maxprocperuid=512
> sysctl -w kern.maxproc=2048
>
> # install postgres
>
> cd "${BASE}"
> log "change directory to ${BASE}"
>
> log "=== install DBMS engine ==="
> postgresql-9.1.2-1-osx.app/Contents/MacOS/installbuilder.sh --mode
> unattended --superaccount PostgresSQL --superpassword Omnis1
> if [ $? != 0 ]; then
>log "install of DBMS failed: ${?}"
>exit 1
> fi
>
> It appears execution stops there. The following is in the system log:
>
> 1/30/12 3:41:26.784 PM markphillips: PRM Installer: === install DBMS
> engine ===
> 1/30/12 3:41:26.819 PM authexec: executing
> /Users/markphillips/Downloads/PRM Installer/Install
> PRM.app/Contents/Resources/postgresql-9.1.2-1-osx.app/Contents/MacOS/osx-intel
> 1/30/12 3:41:49.097 PM osx-intel: kCGErrorInvalidConnection:
> CGSGetWindowTags: Invalid connection
> 1/30/12 3:41:49.097 PM osx-intel: kCGErrorFailure: Set a breakpoint @
> CGErrorBreakpoint() to catch errors as they are logged.
>
> Please note the lack of the terminating message "install of DBMS failed".
> There are other termination log messages that might have been written if
> the script progressed further. None were logged so I assume the script was
> aborted while running the postgresql install script.
>
> Thank you,
>
> - Mark
>
>
>
&
Re: [BUGS] BUG #6404: postgres account not created during unattended install
On Fri, Feb 3, 2012 at 10:37 PM, Mark Phillips
wrote:
> Thank you for the reply. I have spent the better part of this week on this
> and related issues.
>
> My test procedure is as follows: create VM using Fusion 4.x with a fresh
> install of OS X 10.7. The VM is hosted on a Mac also running 10.7. I create
> a snapshot of this clean image. The first step of each test run is
> to restore the snapshot image.
>
> With this in mind, the comment about the previous installation does not
> seem to apply to my report.
>
> After considering your remarks and modifying the app install script, the
> app installation completes normally with a functioning PostgreSQL
> installation. However, the errors reported previous still appear in the
> logs.
>
If erros which you sent last tim appear even when you run the installation
first time, it means that there was an existing installation of postgres.
You can confirm same by checking /etc/postgres-reg.ini file.
>
> The unattended mode results in the appearance of a user "PostgreSQL" in
> the User Accounts preferences panel as well as the login window. It is
> interesting to note that a user named "postgres" in any variant does not
> appear in /Users/ directory, nor in the file /etc/passwd/, with the
> exception of the os x standard postgres account.
> $ cat /etc/passwd | grep "Postgre"
> _postgres:*:216:216:PostgreSQL Server:/var/empty:/usr/bin/false
>
I agree that _postgres exists because of the inbuilt pg which is bundled
with OS. But not sure why PostgreSQL user is there.
>
> The "one click" installer does not result in the appearance of the
> "PostgreSQL" user account in the os x GUI.
>
> To recap the questions:
> 1. are the errors reported in the postgres install log of a type to cause
> a malfunction for end users?
>
Even if the error (postgres user not found) is there in the log, it will
not cause any problem to the end user. Error is coming because installer
finds a previous installation of PG hence tries to stop the existing pg
server if it is running. So even if it is not able to stop any, it is not
going to cause any issue as subsequent installation of pg goes fine.
> 2. how can I suppress the appearance of the user account "PostgreSQL" in
> the os x login window?
>
Please check /etc/postgres-reg.ini file for bindled pg installation.
>
> Many thanks,
>
> - Mark
>
> On Jan 30, 2012, at 11:34 PM, Dharmendra Goyal wrote:
>
> Hi Mark,
>
> Install log shows that your db installation is successful. The error which
> you had sent is coming because your earlier installation failed to create
> 'postgres' user and when you ran the installer again, installer read
> /etc/postgres-reg.ini file to check any previous installation and found
> that previous installation was done. Hence installer tries to stop the db
> server in case it is running using postgres user. This command fails as
> postgres user was not created in your first installation because of some
> reason. But in latest installation (for which you have sent the log),
> postgres user has been created successfully and installation went
> successfully. You need to check why postgres user was not created in first
> go by checking logs of that installation.
>
> You are checking return status of the installbuilder.sh command run which
> is not 0 hence you are getting error ("install of DBMS failed".) in your
> script. Can yu please check what is the return value in your script of
> installbuilder.sh.
>
> Regards,
>
> On Tue, Jan 31, 2012 at 5:37 AM, Mark Phillips > wrote:
>
>>
>> On Jan 29, 2012, at 11:07 PM, Dharmendra Goyal wrote:
>>
>> On Sat, Jan 21, 2012 at 3:01 AM, wrote:
>>
>>> The following bug has been logged on the website:
>>>
>>> Bug reference: 6404
>>> Logged by: Mark Phillips
>>> Email address: mark.phill...@mophilly.com
>>> PostgreSQL version: 9.1.2
>>> Operating system: Mac OS X 10.7
>>> Description:
>>>
>>> for a stand alone app that uses postgres, the app installer invokes the
>>> shell script installbuilder.sh for the "unattended" install of postgres.
>>>
>>> The pg installer creates a user "PostgreSQL" that is not hidden, but does
>>> not create a hidden account "postgres". As a result, the invocation of
>>> pg_ctl fails. Error is "unknown login: postgres".
>>>
>> pg installer creates "postgres" user which somehow seems to be failing at
>> your machine. Can you please send installation log which can be found under
>> /tmp/install-postgresql.log. Also
