Page Index Toggle Pages: 1 ... 3 4 [5] 6  Send Topic Send Topic Print Print
Very Hot Topic (More than 25 Replies) Sesame Server on Linux (Read 31856 times)
Steve_in_Texas
Senior Member
*****
Offline


No personal text

Posts: 893
Location: San Antonio
Joined: Feb 21st, 2004
Re: Sesame Server on Linux
Reply #60 - Oct 23rd, 2011 at 6:50pm
Print Post Print Post  
oops, my local connection was also dropped.
  
Back to top
IP Logged
 
The Cow
YaBB Administrator
*****
Offline



Posts: 2530
Joined: Nov 22nd, 2002
Re: Sesame Server on Linux
Reply #61 - Oct 23rd, 2011 at 7:18pm
Print Post Print Post  
Steve_in_Texas wrote on Oct 23rd, 2011 at 6:50pm:
oops, my local connection was also dropped.


Sesame2, whether for Windows or Linux, does require reliable network connections. Sesame3 should be somewhat more forgiving.
  

Mark Lasersohn&&Programmer&&Lantica Software, LLC
Back to top
IP Logged
 
Steve_in_Texas
Senior Member
*****
Offline


No personal text

Posts: 893
Location: San Antonio
Joined: Feb 21st, 2004
Re: Sesame Server on Linux
Reply #62 - Oct 23rd, 2011 at 9:34pm
Print Post Print Post  
I think the problem is deeper than just a 'flaky network'. Clients are getting booted after only a few seconds, so something must be out of whack.

Moved sesame server back to the new pc after ANOTHER reboot, and all seems fine now.
  
Back to top
IP Logged
 
Steve_in_Texas
Senior Member
*****
Offline


No personal text

Posts: 893
Location: San Antonio
Joined: Feb 21st, 2004
Re: Sesame Server on Linux
Reply #63 - Oct 24th, 2011 at 4:15pm
Print Post Print Post  
Monday morning, local users are staying connected and sesame is running like a champ!  Hope it sticks.

Still some issues with remote clients (a frozen client while browsing records) which Sesame3 may cure.

We're back in high-gear! Seems like the server PC just needed one more reboot.


  
Back to top
IP Logged
 
Steve_in_Texas
Senior Member
*****
Offline


No personal text

Posts: 893
Location: San Antonio
Joined: Feb 21st, 2004
Re: Sesame Server on Linux
Reply #64 - Nov 1st, 2011 at 6:04pm
Print Post Print Post  
Sesame clients and server have been 100% stable and fast for 7 days straight. I have refrained from making any changes in the past 10 days.

In a few days, I will attempt to move Sesame Server back to the original Linux box and see if the stability holds. (I am tempted to install the newest OS with 32-bit lib files on that box, first.)

Steve
  
Back to top
IP Logged
 
Rick_R
Full Member
***
Offline



Posts: 243
Joined: Jan 29th, 2010
Re: Sesame Server on Linux
Reply #65 - Nov 16th, 2011 at 7:37pm
Print Post Print Post  
I ran across this in a review of SUSE's latest Linux distribution:

"Want to run a private cloud? No problem. OpenSUSE comes with customized Eucalyptus, OpenNebula and OpenStack. It also supports ownCloud 2. This is a do-it-yourself Web-based storage cloud application. OpenSUSE claims that “ownCloud is different from solutions like Google Docs, Dropbox or Ubuntu One in that it lets you own the data."

http://www.zdnet.com/blog/open-source/opensuses-new-linux-distribution-is-for-th...
  
Back to top
 
IP Logged
 
Rick_R
Full Member
***
Offline



Posts: 243
Joined: Jan 29th, 2010
Re: Sesame Server on Linux
Reply #66 - Dec 10th, 2011 at 4:22am
Print Post Print Post  
Right now I'm trying LinuxMint 12 ("Lisa") which is based on the latest version of Ubuntu.  I'm actually running a "live" DVD.

The latest version of Ubuntu, 11.10 uses Ubuntu's new Unity interface, with an option to use Gnome 3 instead. A lot of users, including me, don't like either of them. They both have a very kludgy, "Gotta know exactly what you want to do in order to start" feeling. Ubuntu 11.10 no longer supports Gnome 2.

Gnome 2 has a simple menu bar across the top with drop-down text menus. The Mint group is in the process of developing their own interface that will fit on top of Gnome 3 and make it have the look and feel of Gnome 2 while allowing access to the Gnome 3 features.

Mint 12's default interface has a look and feel fairly similar to Windows 7, with the start menu in the lower left-hand corner.

According to an article by Steven J. Vaughan-Nichols at ZDNet, Mint is now the most popular Linux distribution and Ubuntu has dropped to fourth place and according to another article by him (I can't find at the moment) Ubuntu has been in a steady decline for several years.

http://www.zdnet.com/blog/open-source/the-most-popular-linux-is/9913?tag=content...
http://www.zdnet.com/blog/open-source/linux-mint-12s-three-desktops/9919

I've been using Ubuntu for over a year and I've only been using Mint literally a few minutes and it already feels a lot more comfortable than Ubuntu's Unity interface. Although Gnome 3 is different from Unity, it too just feels incredibly awkward.  I'm going to be installing Mint on one of my extra drives and I'll probably be switching to that for Linux.
  
Back to top
 
IP Logged
 
Rick_R
Full Member
***
Offline



Posts: 243
Joined: Jan 29th, 2010
Major problems with Ubuntu 12.04
Reply #67 - May 10th, 2012 at 5:08am
Print Post Print Post  
If anyone is looking to update to Ubuntu 12.04 desktop, there are major problems with the video drivers. In many cases, whether using an on-line update or an install disk, the system loads the initial Ubuntu splash screen (Ubuntu in white, moving dots in red), the screen goes black, and then ... nothing. The video card is outputting a signal, since the monitor doesn't show "no signal".

With 11.10 and an NVidia video card, sometimes it would initialize to just purple--but you could still type in your password and when it accepted that it would initialize properly, and if you then logged out it would stay correct.  Annoying but still usable. That's not what happens with 12.04.

It doesn't seem limited to particular hardware, although most of the people complaining about it are using NVidia hardware.  It has also been reported on Radeon hardware. You can't use the install disk to do a disk repair because the install disk has the same problem.  Judging from the on-line comments it doesn't seem limited to just one build (32-bit, 64-bit, Intel/AMD).

Various people are recommending various workarounds, but they all are roughly equivalent to manually editing an old-style Windows .ini file -- if you know which file to edit.  Unlike Windows, the operating system is spread out over I'd say more than 100 subfolders. I tried booting from the 11.10 CD and then editing the appropriate video config file but none of the recommended workarounds say where that is.  They all assume you can get some kind of video and then run a config program from a terminal.

LinuxMint 12, which is based on 11.10, doesn't have these problems.  The LinuxMint project says that because their distro is based on Ubuntu their new version normally is distributed a month after the latest Ubuntu version. However, they have already forked the desktop and they're saying they're not fully compatible with Ubuntu.
  
Back to top
 
IP Logged
 
carsten
Junior Member
**
Offline


Carpe Diem

Posts: 74
Location: Germany
Joined: Aug 24th, 2005
Re: Sesame Server on Linux
Reply #68 - Jun 6th, 2014 at 11:40am
Print Post Print Post  
HI there,
I am somewhat fighting with sesame on ubuntu here too. I am setting up the server on ubuntu running sesame as a deamen, the software being located in the home of the users "sesame" under ~seame/bin/Sesame2.
I am porting from a Windows server with a 3-user license. Now wher do I place the license and rootdirs.ini files?
I have tried the Sesame2, Sesame2/Program and Sesame2/bin (where the start-script is located) directories to no avail.
Any help higly apreciated!!!
best C.
  

Carsten&&The Houseman&&"Smiling improves your face value"&&"A Clean House is a Sign of a Wasted Life"&&"Rather Big and Hard then Micro and Soft"
Back to top
 
IP Logged
 
The Cow
YaBB Administrator
*****
Offline



Posts: 2530
Joined: Nov 22nd, 2002
Re: Sesame Server on Linux
Reply #69 - Jun 6th, 2014 at 3:15pm
Print Post Print Post  
The license file needs to be in the current working directory for the Sesame process. That path is determined by how you invoke the process. There are several different ways to do so in Linux.

If you want to make sure that it is always uses the same license path, no matter how Sesame is invoked, you need to set the environment variable "SESAME_LICENSE_PATH" to the full path (including filename) where the license file resides.
  

Mark Lasersohn&&Programmer&&Lantica Software, LLC
Back to top
IP Logged
 
carsten
Junior Member
**
Offline


Carpe Diem

Posts: 74
Location: Germany
Joined: Aug 24th, 2005
Re: Sesame Server on Linux
Reply #70 - Jun 7th, 2014 at 9:32am
Print Post Print Post  
Hi MArk,
thanks for your quick reply, long time no hear!!

I tried to set the variable in the /etc/environment file to make it available at boot. It does not seem to work, however I will have to try again on Monday, cause my remote connection has crashed/rdp does not start anymore.
On my second problem: where does the rootdir.ini have to be.
regards
Carsten
  

Carsten&&The Houseman&&"Smiling improves your face value"&&"A Clean House is a Sign of a Wasted Life"&&"Rather Big and Hard then Micro and Soft"
Back to top
 
IP Logged
 
The Cow
YaBB Administrator
*****
Offline



Posts: 2530
Joined: Nov 22nd, 2002
Re: Sesame Server on Linux
Reply #71 - Jun 7th, 2014 at 1:53pm
Print Post Print Post  
If you using the system-wide "/etc/environment" file, you should be able to check whether it is correct with printenv or export (with no arguments). Remember it is the full path, including filename.

The environment variable for the rootdirs file is "SESAME_ROOTDIRS_PATH". It is also the full path with filename.

You can skip setting either of these variables by determining where you CWD is when you launch, and placing the files there. Both the various shells and Sesame itself have means of reporting the CWD.
  

Mark Lasersohn&&Programmer&&Lantica Software, LLC
Back to top
IP Logged
 
carsten
Junior Member
**
Offline


Carpe Diem

Posts: 74
Location: Germany
Joined: Aug 24th, 2005
Re: Sesame Server on Linux
Reply #72 - Jun 12th, 2014 at 2:06pm
Print Post Print Post  
Hi Mark,
after including the variables in the startscript in /etc/init.d and explictely exporting them it is now working, tanks for your help here.
However, I have now encountered a far more serious problem now:
All number, figures, ammounts etc are interpreted strangely!
I have written a booking program for a travel agent that has been running for 9 years now on a MessyWindows PC.
We had planned to move it to linux (Ubuntu 12.04) now for quite some time. Since the Windwos-PC is breaking down, now was the time!
The effect now is that all bookings and all relate information (available rooms, prices etc) are screwed-up. E.g. a trip cositing 799€ now is somewhat like 400Billion!!
Any idea?
I could provide you the databse, if you give me your email.
best Carsten
  

Carsten&&The Houseman&&"Smiling improves your face value"&&"A Clean House is a Sign of a Wasted Life"&&"Rather Big and Hard then Micro and Soft"
Back to top
 
IP Logged
 
The Cow
YaBB Administrator
*****
Offline



Posts: 2530
Joined: Nov 22nd, 2002
Re: Sesame Server on Linux
Reply #73 - Jun 12th, 2014 at 4:22pm
Print Post Print Post  
That sounds like you are having "locale" issues with the OS and numbers. Check what the OS thinks you are using for a decimal point and for the thousands separator. Then check what Sesame is using. Make sure both agree with what you were using when the data was entered and what you want to use in the future.
  

Mark Lasersohn&&Programmer&&Lantica Software, LLC
Back to top
IP Logged
 
carsten
Junior Member
**
Offline


Carpe Diem

Posts: 74
Location: Germany
Joined: Aug 24th, 2005
Re: Sesame Server on Linux
Reply #74 - Jun 12th, 2014 at 6:00pm
Print Post Print Post  
I have experimented a bit more and it seems the error only occurs when Sesame is started during the boot process of the server (i.e. via init.d). If I start it manually invoking the script in /etc/init.d it will run fine (just the € sign is screwed up!!!).

Here is the startscrip I use in init.d

--------------- Start ---------------

#! /bin/sh

PATH=/sbin:/usr/sbin:/bin:/usr/bin:/home/sesame/bin/Sesame2
SESAME_LICENSE_PATH=/home/sesame/bin/Sesame2/s_license2.lic
SESAME_ROOTDIRS_PATH=/home/sesame/bin/Sesame2/rootdirs.ini
export "PATH" "SESAME_LICENSE_PATH" "SESAME_ROOTDIRS_PATH"


### BEGIN INIT INFO
# Provides:          skeleton
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Example initscript
# Description:       This file should be used to construct scripts to be
#                    placed in /etc/init.d.
### END INIT INFO

# Author: Carsten Rietbrock <crietbrock@yahoo.de>
#
# Please remove the "Author" lines above and replace them
# with your own name if you copy and modify this script.

# Do NOT "set -e"

# PATH should only include /usr/* if it runs after the mountnfs.sh script
DESC="Sesame_Server"
NAME=sesame
DAEMON=/home/sesame/bin/Sesame2/Program/$NAME
DAEMON_ARGS="-daemon -server pampeago.dyndns.org "
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
# USERID=sesame

# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0

# Read configuration variable file if it is present
[ -r /etc/default/$NAME ] && . /etc/default/$NAME

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
# and status_of_proc is working.
. /lib/lsb/init-functions

#
# Function that starts the daemon/service
#
do_start()
{
     # Return
     #   0 if daemon has been started
     #   1 if daemon was already running
     #   2 if daemon could not be started
     start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \
           || return 1 &
     start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
           $DAEMON_ARGS \
           || return 2 &
     # Add code here, if necessary, that waits for the process to be ready
     # to handle requests from services started subsequently which depend
     # on this one.  As a last resort, sleep for some time.
}

#
# Function that stops the daemon/service
#
do_stop()
{
     # Return
     #   0 if daemon has been stopped
     #   1 if daemon was already stopped
     #   2 if daemon could not be stopped
     #   other if a failure occurred
     start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
     RETVAL="$?"
     [ "$RETVAL" = 2 ] && return 2 &
     # Wait for children to finish too if this is a daemon that forks
     # and if the daemon is only ever run from this initscript.
     # If the above conditions are not satisfied then add some other code
     # that waits for the process to drop all resources that could be
     # needed by services started subsequently.  A last resort is to
     # sleep for some time.
     start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
     [ "$?" = 2 ] && return 2 &
     # Many daemons don't delete their pidfiles when they exit.
     rm -f $PIDFILE
     return "$RETVAL"
}

#
# Function that sends a SIGHUP to the daemon/service
#
do_reload() {
     #
     # If the daemon can reload its configuration without
     # restarting (for example, when it is sent a SIGHUP),
     # then implement that here.
     #
     start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
     return 0 &
}

case "$1" in
  start)
     [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
     do_start
     case "$?" in
           0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
           2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
     esac
     ;;
  stop)
     [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
     do_stop
     case "$?" in
           0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
           2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
     esac
     ;;
  status)
       status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
       ;;
  #reload|force-reload)
     #
     # If do_reload() is not implemented then leave this commented out
     # and leave 'force-reload' as an alias for 'restart'.
     #
     #log_daemon_msg "Reloading $DESC" "$NAME"
     #do_reload
     #log_end_msg $?
     #;;
  restart|force-reload)
     #
     # If the "reload" option is implemented then remove the
     # 'force-reload' alias
     #
     log_daemon_msg "Restarting $DESC" "$NAME"
     do_stop
     case "$?" in
       0|1)
           do_start
           case "$?" in
                 0) log_end_msg 0 ;;
                 1) log_end_msg 1 ;; # Old process is still running
                 *) log_end_msg 1 ;; # Failed to start
           esac
           ;;
       *)
            # Failed to stop
           log_end_msg 1
           ;;
     esac
     ;;
  *)
     #echo "Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload}" >&2
     echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
     exit 3
     ;;
esac

:

--------------------- End --------------

  

Carsten&&The Houseman&&"Smiling improves your face value"&&"A Clean House is a Sign of a Wasted Life"&&"Rather Big and Hard then Micro and Soft"
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1 ... 3 4 [5] 6 
Send Topic Send Topic Print Print