Installing EDB release 2 on a Dutch SuSE Linux 10

Hi,

I've just installed a fresh copy of SuSE 10 with texts in Dutch. Installing EDB and even running Studio after checking 'run studio now' works well, but..... when I quitted Studio and I restarted Studio I received the dreaded nightmare in the form of a "Segmentatiefout". This is the same as "Segmentartion Fault" at the same point on which Studio crashed under a Dutch Windows. This looks like the infamous translation-related error in the past. I've uninstalled the package for now, but if the error is solved, I'll reinstall it again.

With regards from,
Tom van der Vlugt

Dear Tom,

Can you please let us know whether you are using the SuSE Linux 10 on a 64 Bit machine? And also results when you try using EDB-Studio with language set as English?

This will help us narrow down the problem.

Regards,

Hi,

I'm running SuSE 10 on a Pentium III @ 800 Mhz, pretty old computer...

I've reinstalled the product after setting the languahe to English/US using Yast, a setting program specific to SuSE. I installed the edb program under the root account, since I want to get it installed under /opt

I'm getting the following results upon invoking ./edb-studio:

1. Logging in as tom (my normal account) presents me the splash screen and just after the main screen of studio, the program crashes with the dreadful segmentation fault. This is an unworkable situation. :-(

2. Logging in as root (super user account) provides me with a successful startup and working of the nice studio. This is a perfectly workable situation, but it compromises the security.

3. Logging in as enterprisedb provides me with the studio, but the server seems to have vanished! This is an unworkable situation. :-(

I've installed the product without strange options and I've assigned the installer to install the postmaster as a daemon.

Did I forget something.

With regards from a wet and bleak Holland from,
Tom

Hi,

I also have installed the newest Java 2 SDK, 1.5.0_05, and the NetBeans 4.1 Java2 IDE. I successfully set up a JDBC connection against my home brewed edb database KA. It runs perfectly in Java.

The fact that edb-studio gets awry unless started by root raises me question-marks. However under root edb-studio works great! This looks like a rights problem...

With regards from,
Tom

Hi,

edb-studio:
-----------
I've forgotten to tell something about the (in)ability to work with edb-studio as result in my comments in this thread. edb2005 has been installed using the console mode of the InstallShield installer.

I've told about that the edb server seems to have vanished when I invoke edb-studio from user enterprisedb, but in fact the server exists and it's running.

After this shocking event an invoke of edb-studio from root always gives me a working situation.

Invoking edb-studio from tom still presents me the dreaded segmentation fault.

Whatever I do, these three results are 100% reproducible in my case. One failure does not lead to another failure! These failures are completely independent and depend on the user who's trying to invoke edb-studio.

JDBC connector:
---------------

Regardless the user connects to edb using JDBC, I always successfully get a connection to edb-server.

Java rocks! NetBeans has a nice db console interface resembling edb-studio. Users root and tom successfully connect to edb, wow!

Daemon:
-------

Upon startup the edb-server and the autovacuum daemon successfully start up. Upon reboot or shutdown both servers end successfully.

With regards from,
Tom

Dear Tom,

Your queries can be answered by categorizing them into three parts:

EDB-Studio using “root” user:
-------------------------------
EDB-Studio works perfectly fine in this scenario and you do not get any errors while you are logged in as “root”.

EDB-Studio using “enterprisedb” user:
--------------------------------------
EDB-Studio launches perfectly fine but you cannot see the servers listed there. You can do that using the button at the left corner of EDB-Studio menu bar “Add a connection to server”. Click that and then provide the appropriate database server information and click OK. This way you can connect to the database server already running as a daemon.

EDB-Studio using “tom” user:
------------------------------
The segmentation fault may be because this user (“tom”) doesn’t belong to “edb” user group that the other “enterprisedb” user belongs to or it can be that this user doesn’t have the appropriate rights associated which are same like the “enterprisedb” user. You can also try, using the same user “tom” when you are are asked to provide a username during EnterpriseDB installation process.

If using “tom” doesn’t work out you can always try “enterprisedb” user in order to use EDB-Studio, as “enterprisedb” is also not an admin user.

Hope this helps ..

Regards,

Hi,

The problem whilst invoking from user "enterprisedb" has been solved.

So, the security issue using "root" has also been solved.

It's no issue anymore that I can't run edb-studio from user "tom", since "enterprisedb" is the appropriate user to work with edb-studio. But, a "segmentation fault" isn't very friendly. If this segfault is caused by access rights, I should expect a message like 'User "tom" doesnt belong to the edb group, access denied!'. This looks like a fall-through through an error/exception handler.
Question: is it possible to catch segfaults like ordinary C++ exceptions using try/catch?

By the way, I've seen my testimonial on your page, great! You are indeed listening to your customers! I wish that all companies act like you do, since then the world had been far better than that it now is.

Keep up the good works!
With regards from,
Tom

Hi,

I've added my very own account to the group "edb", but the same segfault occurs using account "tom".

Is adding my account to group "edb" sufficient or did I forget something more?

I've used yast -> security & users -> user management
I've then selected my account "tom" and I activated 'edb' under the listbox Groups. Before I did my test, I completely logged out and logged in again. The segfault didn't vanish.

With regards from,
Tom

Ok, it isn't a masjor problem at all anymore that user 'tom' cannot invoke edb-studio correctly. I still consider that only user 'enterprisedb' is entitled to invoke edb-studio.

You've stated that I could re-install the product. I don't do want to do that again, since I had a bitch of a time to hunt for installation errors like 'port already used' or 'product already installed'. Now I've a good working system and if it ain't broke don't fix it... ;-) User 'enterprisedb' is the user for major maintenance work and nobody else!

The finest part of this package is our JDBC connector! I succeeded in creating a connection to edb and I can work with it. So the segfault issue regarding user 'tom' is now a mere minor issue, since the same user 'tom' can connect to the database using JDBC. JDBC ==

Regards from Tom

Dear Tom,

I also tried myself using the same normal user like "tom" in your case, but was not able to replicate the scenario of Segmentation fault. There might be some settings you had done for that specific user which is causing this issue.
It is always recommended to use the user "enterprisedb" that was created during the install process for using EnterpriseDB tools.

We always appreciate customer feedback and have based our features list on user demand.

Thanks,

We will be trying out different scenarios to replicate the segmentation fault in our lab and hopefully you will have fix for this in the upcoming releases

Thanks for the detailed scenarios you listed as they will help us narrow down the cause.

Regards,

Hi,

I've attempted again to get rid of that darned segmentation fault using the following:

1. Login as user 'tom' (now as member of group 'users')
2. command 'startx' issued
3. Upon arrival in x-window I clicked for a terminal (konsole)
4. command 'newgrp edb' issued
5. command 'cd /opt/edb/8.0.4.15/studio/bin' issued
6. command './edb-studio' issued after splash screen segmentation fault. :-(

This means that common users, members of group 'users' are still locked from working with the studio. Differences in access rights should not trigger any segmentation faults.

I now give you some details of the technical parts of my system installed with SuSE 10.0 OSS version:

uname -a:
Linux linux 2.6.13-15-default #1 Tue Sep 13 14:56:15 UTC 2005 i686 i686 i386 GNU/Linux

gcc --version:
gcc (GCC) 4.0.2 20050901 (prerelease) (SUSE Linux)
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

set:
ACLOCAL_FLAGS='-I /opt/gnome/share/aclocal'
BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="3" [1]="00" [2]="16" [3]="1" [4]="release" [5]="i586-suse-linux")
BASH_VERSION='3.00.16(1)-release'
COLORTERM=
COLUMNS=80
CPU=i686
CVS_RSH=ssh
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-JvmYuhGB9L,guid=d9988d43376209b58da6d7d08abf6e00
DESKTOP_LAUNCH=kde-open
DIRSTACK=()
DISPLAY=:0.0
EUID=1000
FROM_HEADER=
GNOME2_PATH=/usr/local:/opt/gnome:/usr
GROFF_NO_SGR=yes
GROUPS=()
GS_LIB=/home/tom/.fonts
GTK2_RC_FILES=/etc/opt/gnome/gtk-2.0/gtkrc:/opt/gnome/share/themes//Qt/gtk-2.0/gtkrc:/home/tom/.gtkrc-2.0-qtengine:/home/tom/.kde/share/config/gtkrc-2.0
GTK_PATH=/usr/local/lib/gtk-2.0:/opt/gnome/lib/gtk-2.0:/usr/lib/gtk-2.0
GTK_RC_FILES=/etc/opt/gnome/gtk/gtkrc:/home/tom/.gtkrc:/home/tom/.kde/share/config/gtkrc
G_BROKEN_FILENAMES=1
HISTCONTROL=ignoreboth
HISTFILE=/home/tom/.bash_history
HISTFILESIZE=1000
HISTSIZE=1000
HOME=/home/tom
HOST=linux
HOSTFILE=
HOSTNAME=linux
HOSTTYPE=i386
IFS=$' \t\n'
INFODIR=/usr/local/info:/usr/share/info:/usr/info
INFOPATH=/usr/local/info:/usr/share/info:/usr/info:/opt/gnome/share/info
INPUTRC=/etc/inputrc
JAVA_HOME=/usr/java/jdk1.5.0_05
KDE_FULL_SESSION=true
KDE_MULTIHEAD=false
KONSOLE_DCOP='DCOPRef(konsole-6060,konsole)'
KONSOLE_DCOP_SESSION='DCOPRef(konsole-6060,session-1)'
LANG=en_US
LD_HWCAP_MASK=0x20000000
LESS='-M -I'
LESSCLOSE='lessclose.sh %s %s'
LESSKEY=/etc/lesskey.bin
LESSOPEN='lessopen.sh %s'
LESS_ADVANCED_PREPROCESSOR=no
LINES=24
LOGNAME=tom
LS_COLORS='no=00:fi=00:di=01;34:ln=00;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31:ex=00;32:*.cmd=00;32:*.exe=01;32:*.com=01;32:*.bat=01;32:*.btm=01;32:*.dll=01;32:*.tar=00;31:*.tbz=00;31:*.tgz=00;31:*.rpm=00;31:*.deb=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.zoo=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.tb2=00;31:*.tz2=00;31:*.tbz2=00;31:*.avi=01;35:*.bmp=01;35:*.fli=01;35:*.gif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mng=01;35:*.mov=01;35:*.mpg=01;35:*.pcx=01;35:*.pbm=01;35:*.pgm=01;35:*.png=01;35:*.ppm=01;35:*.tga=01;35:*.tif=01;35:*.xbm=01;35:*.xpm=01;35:*.dl=01;35:*.gl=01;35:*.wmv=01;35:*.aiff=00;32:*.au=00;32:*.mid=00;32:*.mp3=00;32:*.ogg=00;32:*.voc=00;32:*.wav=00;32:'
LS_OPTIONS='-N --color=tty -T 0'
MACHTYPE=i686-suse-linux
MAIL=/var/mail/tom
MAILCHECK=60
MANPATH=/usr/local/man:/usr/share/man:/usr/X11R6/man:/opt/gnome/share/man
MINICOM='-c on'
NNTPSERVER=news
OPTERR=1
OPTIND=1
OSTYPE=linux
PAGER=less
PATH=/home/tom/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/java/jdk1.5.0_05/bin
PIPESTATUS=([0]="0")
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig:/opt/kde3/lib/pkgconfig:/opt/gnome/lib/pkgconfig:/opt/gnome/lib/pkgconfig:/opt/gnome/share/pkgconfig
PPID=6060
PROFILEREAD=true
PS1='$(ppwd \l)\u@\h:\w> '
PS2='> '
PS4='+ '
PWD=/home/tom
PYTHONSTARTUP=/etc/pythonstart
QTDIR=/usr/lib/qt3
SESSION_MANAGER=local/linux:/tmp/.ICE-unix/6028
SHELL=/bin/bash
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
SHLVL=4
TERM=xterm
TEXINPUTS=:/home/tom/.TeX:/usr/share/doc/.TeX:/usr/doc/.TeX
UID=1000
USER=tom
USE_FAM=
WINDOWID=44040199
WINDOWMANAGER='/usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/X11R6/bin/kde'
XAUTHLOCALHOSTNAME=linux
XAUTHORITY=/home/tom/.Xauthority
XCURSOR_THEME=crystalwhite
XDG_CONFIG_DIRS=/usr/local/etc/xdg/:/etc/xdg/:/etc/opt/gnome/xdg/
XDG_DATA_DIRS=/usr/local/share/:/usr/share/:/etc/opt/kde3/share/:/opt/kde3/share/:/opt/gnome/share/
XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB
XMODIFIERS=@im=local
XNLSPATH=/usr/X11R6/lib/X11/nls

Maybe this will help you to reproduce the segfault under user 'tom'.

With regards from,
Tom

Dear Tom,

Please try one more scenario, create a new user for example 'temp'. Now try opening EDB-Studio with this user and let us know the results.

Regards,

Hi,

I've just created a new user 'temp' and tried ./edb-studio. Voila, it came up and like user 'enterprisedb' I only needed to look up the server and this needed only be done once.

Now, I suspect some hidden files in my own home directory, since I've kept my own /home directory during install.

With regards from,
Tom

I'm here again. ;-)

I've decided to delete my account, but before doing that I've saved my data and downloads to a safa place at /usr/tom for temporary usage.

These are the steps:

1. Copy all important documents and files from my home directory to /usr/tom
2. Using Yast delete my account. Very simple to do so
3. Reboot the computer in order to erase /tmp and /var/tmp
4. Loggin in as root to use Yast to add tom again
5. Again a reboot to get rid of stray bytes from /tmp and /var/tmp
6. Logged in as tom
7. cd tom /opt/edb/8.0.4.15/studio/bin
8. ./edb-studio still is giving me that nasty naughty segmentation fault!
9. Now I tried to do 'su -l tom' and repeated step 7 and 8.

No segmentation fault! How is this possible???

Thank you for your suggestion, since it helped at least partially. Your suggestion is logical, but it only fails when I do not use the su command.

Maybe this will help you to thwart this strange naughty segmentation fault.

Regards from,
Tom

Dear Tom,

Working with a different user solved the issue because there might be some settings you had done for the already created user 'tom' and that is why it is resulting in a segmentation fault.

I have tried different scenarios but still not able to replicate the segmentation fault you mentioned.

Regards,

Hi,

I've used 'ulimit -c' to obtain a core-dump for the segmentation fault. Not in this tread, but in a separate mail the core is included.

With regards from,
Tom

Hi,

I've found a temporary pretty neat solution for my infamous segmentation fault:

In /opt/edb-2005/8.0.4.15/studio/bin I've created a shell-script called 'es.sh'. This is its contents:

#!/bin/bash
cd /opt/edb-2005/8.0.4.15/studio/bin/
./edb-studio

In /home/tom/bin I've also created a shell script called 'es.sh'. This is its contents:

#!/bin/bash
su -l tom -c '/opt/edb-2005/8.0.4.15/studio/bin/es.sh'

Both scripts have been made executable.

Beware of the line '#!/bin/bash'. This is SuSE 10 specific at least. Some Linux versions may read '#!/usr/bin/bash'!

If I execute 'es.sh' it asks for my password and then it launches edb-studio WITHOUT segmentation fault.

With regards from,
Tom

Dear Tom,

Thanks for sharing your solution with everyone on the forums

Regards,