Trying to upgrade...
I'm getting this error (trying to point to my database from an earlier version):
%YDB-E-ZGBLDIRACC, Cannot access global directory /home/edm/m/$ydb_gbldir.gld. Cannot continue.

However:

edm@jsrserver2:~/m$ ls -l /home/edm/m/$ydb_gbldir.gld
-rw-rw-r-- 1 edm edm 7680 Jan 5 15:55 /home/edm/m/../.yottadb/r1.34_x86_64/g/yottadb.gld
edm@jsrserver2:~/m$

What should be the value of ydb_gbldir?

Thanks,in advance,
Ed

On Thursday, January 5, 2023 at 4:41:15 PM UTC-5, ed de moel wrote:
> Trying to upgrade...
> I'm getting this error (trying to point to my database from an earlier version):
> %YDB-E-ZGBLDIRACC, Cannot access global directory /home/edm/m/$ydb_gbldir..gld. Cannot continue.
>
> However:
>
> edm@jsrserver2:~/m$ ls -l /home/edm/m/$ydb_gbldir.gld
> -rw-rw-r-- 1 edm edm 7680 Jan 5 15:55 /home/edm/m/../.yottadb/r1.34_x86_64/g/yottadb.gld
> edm@jsrserver2:~/m$
>
> What should be the value of ydb_gbldir?
>
> Thanks,in advance,
> Ed

Ed, the environment variable $ydb_gbldir cannot be embedded within a path, and should itself point to the global directory file. Try setting it to: /home/edm/.yottadb/r134_x86_64/g/yottadb.gld

Regards
– Bhaskar

That's what I had originally.
WHen I set it back, I get this:

edm@jsrserver2:~/m$ echo $ydb_gbldir
home/edm/.yottadb/r1.34_x86_64/g/yottadb.gld
edm@jsrserver2:~/m$ env | grep ydb
ydb_dist=/usr/local/lib/yottadb/r136
ydb_sysid=jsrserver2
ydb_rel=r1.36_x86_64
ydb_routines=. /usr/local/lib/yottadb/r136
ydb_gbldir=home/edm/.yottadb/r1.34_x86_64/g/yottadb.gld
ydb_dir=/home/edm/.yottadb
edm@jsrserver2:~/m$ sudo /usr/local/lib/yottadb/r136/mumps -direct
[sudo] password for edm:

YDB>s ^edm=1
%YDB-E-ZGBLDIRACC, Cannot access global directory /home/edm/m/$ydb_gbldir.gld. Cannot continue.
%SYSTEM-E-ENO2, No such file or directory

YDB>

So... it looks like there is something else that prepends the current directory and appends the .gld
Any suggestions?

Thanks,
Ed

On Thursday, January 5, 2023 at 5:23:21 PM UTC-5, ed de moel wrote:
> That's what I had originally.
> WHen I set it back, I get this:
>
> edm@jsrserver2:~/m$ echo $ydb_gbldir
> home/edm/.yottadb/r1.34_x86_64/g/yottadb.gld
> edm@jsrserver2:~/m$ env | grep ydb
> ydb_dist=/usr/local/lib/yottadb/r136
> ydb_sysid=jsrserver2
> ydb_rel=r1.36_x86_64
> ydb_routines=. /usr/local/lib/yottadb/r136
> ydb_gbldir=home/edm/.yottadb/r1.34_x86_64/g/yottadb.gld
> ydb_dir=/home/edm/.yottadb
> edm@jsrserver2:~/m$ sudo /usr/local/lib/yottadb/r136/mumps -direct
> [sudo] password for edm:
>
> YDB>s ^edm=1
> %YDB-E-ZGBLDIRACC, Cannot access global directory /home/edm/m/$ydb_gbldir..gld. Cannot continue.
> %SYSTEM-E-ENO2, No such file or directory
>
> YDB>
>
> So... it looks like there is something else that prepends the current directory and appends the .gld
> Any suggestions?
>
> Thanks,
> Ed

I'm not sure what the sudo is doing for you in "sudo /usr/local/lib/yottadb/r136/mumps -direct", but the sudo'd process does not inherit the environment variables of the sudo'ing process. Try "sudo -E ..." if you must sudo, or drop the sudo.

Regards
– Bhaskar

I think I found it.
I did a re-install (with --override-existing), which gave me some new error messages.
Then I un-set all environment variables with ydb_* in my .bashrc, and started from scratch.
This seems to work.

Thanks,
Ed

Getting a new error:
%YDB-E-RELINKCTLERR, Error with relink control structure for $ZROUTINES directory /home/edm/.yottadb/r1.36_x86_64/o/utf8
%YDB-E-SYSCALL, Error received from system call open() of file /tmp/yottadb/r1.36_x86_64/ydb-relinkctl-49331a2ee86be3f64fe65b2666eaba1c failed -- called from module /Distrib/YottaDB/R136/sr_unix/relinkctl.c at line 323
%SYSTEM-E-ENO2, No such file or directory

There doesn't appear to be a directory named /tmp/yottadb

Any hints?
Thanks,
Ed

Apparently, the system cannot recompile a routine.
Here are my environment variables:

edm@jsrserver2:~/m$ env | grep ydb
ydb_dist=/usr/local/lib/yottadb/r136
ydb_sysid=jsrserver2
ydb_log=/tmp/yottadb/r1.36_x86_64
ydb_rel=r1.36_x86_64
ydb_routines=. /home/edm/.yottadb/r1.36_x86_64/o/utf8*(/home/edm/.yottadb/r1.36_x86_64/r /home/edm/.yottadb/r) /usr/local/lib/yottadb/r136/utf8/libyottadbutil.so
ydb_chset=UTF-8
ydb_tmp=/tmp/yottadb/r1.36_x86_64
ydb_gbldir=/home/edm/.yottadb/r1.36_x86_64/g/yottadb.gld
ydb_icu_version=70.1
ydb_dir=/home/edm/.yottadb
edm@jsrserver2:~/m$

Recompiling with those settings worked fine until some time yesterday.
Earlier today, it still worked fine with some routines.
Now it even fails with those routines...

HELP!

On Wednesday, January 11, 2023 at 9:43:45 AM UTC-5, ed de moel wrote:
> Apparently, the system cannot recompile a routine.
> Here are my environment variables:
> edm@jsrserver2:~/m$ env | grep ydb
> ydb_dist=/usr/local/lib/yottadb/r136
> ydb_sysid=jsrserver2
> ydb_log=/tmp/yottadb/r1.36_x86_64
> ydb_rel=r1.36_x86_64
> ydb_routines=. /home/edm/.yottadb/r1.36_x86_64/o/utf8*(/home/edm/.yottadb/r1.36_x86_64/r /home/edm/.yottadb/r) /usr/local/lib/yottadb/r136/utf8/libyottadbutil.so
> ydb_chset=UTF-8
> ydb_tmp=/tmp/yottadb/r1.36_x86_64
> ydb_gbldir=/home/edm/.yottadb/r1.36_x86_64/g/yottadb.gld
> ydb_icu_version=70.1
> ydb_dir=/home/edm/.yottadb
> edm@jsrserver2:~/m$

Ed –

When you specify and object directory with an asterisk suffix, e.g., /home/edm/.yottadb/r1.36_x86_64/o/utf8*, it means that auto-relink (a publish-subscribe way for processes to automatically execute the latest object code of routines) discussed in https://docs.yottadb.com/ProgrammersGuide/isv.html#zroutines-isv) is enabled by that process for files in that directory. The RELINKCTL error (https://docs.yottadb.com/MessageRecovery/errors.html#relinkctlerr) followed by the SYSCALL error suggests that the could not access the auto-relink control file (/tmp/yottadb/r1.36_x86_64/ydb-relinkctl-49331a2ee86be3f64fe65b2666eaba1c). To troubleshoot:

- Does the file /tmp/yottadb/r1.36_x86_64/ydb-relinkctl-49331a2ee86be3f64fe65b2666eaba1c exist, and if so, what are its permissions?
- What does MUPIP RCTLDUMP (https://docs.yottadb.com/AdminOpsGuide/dbmgmt.html#rctldump) say?
- Does a MUPIP RUNDOWN RELINKCTL (https://docs.yottadb.com/AdminOpsGuide/dbmgmt.html#relinkctl) clear the issue?

Regards
– Bhaskar

I'm afraid those commands didn't provide any information.
That file does not exist (in fact, there is nothing at all in /tmp/yottadb):

edm@jsrserver2:~/m$ mupip rctldump
%YDB-E-RELINKCTLERR, Error with relink control structure for $ZROUTINES directory /home/edm/.yottadb/r1.36_x86_64/o/utf8
%YDB-E-SYSCALL, Error received from system call open() of file /tmp/yottadb/r1.36_x86_64/ydb-relinkctl-49331a2ee86be3f64fe65b2666eaba1c failed -- ca
lled from module /Distrib/YottaDB/R136/sr_unix/relinkctl.c at line 323
%SYSTEM-E-ENO2, No such file or directory
edm@jsrserver2:~/m$ ls -l /tmp/yottadb
total 0
edm@jsrserver2:~/m$ mupip rundown relinkctl
MUPIP RUNDOWN only accepts a parameter when -FILE or -REGION is specified.
%YDB-E-MUPCLIERR, Action not taken due to CLI errors
edm@jsrserver2:~/m$

There needed a dash in the mupip rundown, it didn't make any difference though:

edm@jsrserver2:~/m$ mupip rundown -relinkctl
%YDB-I-RLNKCTLRNDWNSUC, Relinkctl file for $ZROUTINES directory /home/edm/.yottadb/r1.36_x86_64/o/utf8 successfully rundown
edm@jsrserver2:~/m$

On Wednesday, January 11, 2023 at 11:04:37 AM UTC-5, ed de moel wrote:
> I'm afraid those commands didn't provide any information.
> That file does not exist (in fact, there is nothing at all in /tmp/yottadb):
>
>
> edm@jsrserver2:~/m$ mupip rctldump
> %YDB-E-RELINKCTLERR, Error with relink control structure for $ZROUTINES directory /home/edm/.yottadb/r1.36_x86_64/o/utf8
> %YDB-E-SYSCALL, Error received from system call open() of file /tmp/yottadb/r1.36_x86_64/ydb-relinkctl-49331a2ee86be3f64fe65b2666eaba1c failed -- ca
> lled from module /Distrib/YottaDB/R136/sr_unix/relinkctl.c at line 323
> %SYSTEM-E-ENO2, No such file or directory
> edm@jsrserver2:~/m$ ls -l /tmp/yottadb
> total 0
> edm@jsrserver2:~/m$ mupip rundown relinkctl
> MUPIP RUNDOWN only accepts a parameter when -FILE or -REGION is specified..
> %YDB-E-MUPCLIERR, Action not taken due to CLI errors
> edm@jsrserver2:~/m$

Ed, the environment variables are telling YottaDB to put the relink control files in the directory ydb_log=/tmp/yottadb/r1.36_x86_64, but it does not exist.

Regards
– Bhaskar

On Wednesday, January 11, 2023 at 12:08:50 PM UTC-5, K.S. Bhaskar wrote:
Ah, thanks.
Indeed, now that error is gone.

Got a little further.
Things now run smoothly when I run them from a terminal, but when I access things through the webserver (apache2),
I get:

%YDB-E-NONUTF8LOCALE, Locale has character encoding (ANSI_X3.4-1968) which is not compatible with UTF-8 character set

all ydb_* environment variables are set up the same as for a terminal session.

So, obviously, I forgot to set up the "locale" for UTF-8. How would I do that?
Thanks,
Ed

Found that one: it's a setting in Apache.
On to the next step.

On Wednesday, January 11, 2023 at 6:57:20 PM UTC-5, ed de moel wrote:
> Found that one: it's a setting in Apache.
> On to the next step.

You optionally generate the locales you need (some are there by default) and choose one. For example, on my laptop:

$ locale -a
C C.UTF-8
en_US.utf8
POSIX
$ echo $LANG
en_US.utf8
$

Regards
– Bhaskar

On Wednesday, January 11, 2023 at 9:29:19 PM UTC-5, K.S. Bhaskar wrote:
> On Wednesday, January 11, 2023 at 6:57:20 PM UTC-5, ed de moel wrote:
> > Found that one: it's a setting in Apache.
> > On to the next step.
> You optionally generate the locales you need (some are there by default) and choose one. For example, on my laptop:
>
> $ locale -a
> C
> C.UTF-8
> en_US.utf8
> POSIX
> $ echo $LANG
> en_US.utf8
> $
>
> Regards
> – Bhaskar

Ed, at your convenience, please let me know how things are working for you. Thank you.

Regards
– Bhaskar

On the YottaDB side, all is fine now.
I'm still having an issue with Apache, I'm sure I'll figure that one out over the weekend.
Thanks again for your help,
Ed

But... something to know for other people:
I just ran a
sudo apt upgrade
and , lo and behold, the /tmp/yottadb/r1.36_x86_64 directory disappeared again.
No that I know that I just have to create it again, no problem, but, slightly inconvenient.

Would it be better to use a directory for ydb_log en ydb_tmp that is somewhere under /home/edm?

On Friday, January 13, 2023 at 10:40:39 AM UTC-5, ed de moel wrote:
> But... something to know for other people:
> I just ran a
> sudo apt upgrade
> and , lo and behold, the /tmp/yottadb/r1.36_x86_64 directory disappeared again.
> No that I know that I just have to create it again, no problem, but, slightly inconvenient.
>
> Would it be better to use a directory for ydb_log en ydb_tmp that is somewhere under /home/edm?

Yes, the default is under /tmp so that when you reboot it goes away. Since all users need to have access to the $ydb_tmp directory, if it goes under /home/edm, then user bhaskar won't be able to access it unless you change the permissions. Production systems typically explicitly set ydb_tmp and other environment variables.

Regards
– Bhaskar