Forum Replies Created
-
AuthorReplies
-
Thanks for your reply. How did you accomplish the this? Did you call a java method, or use tdom, or is it built into cloverleafs web service client?
Keith,
Thanks for the reply. I don’t want to shut down all threads, its a dynamic set based on users input, but when they user makes their selection it would apply just that selection to the command.
Yes, to be fair, I had my own system in place that queried the DB more frequently and ended up causing more issues. When we went to global monitor we saw a reduction in errors.
I think this highlights the need for Cloverleaf to move to a more robust default db structure.
I also want to play with the execution user, which is a parameter on a lot of commands, to see if that improves the situation.
It turns out that global monitor starts up a monitor daemon (Assuming its set to do so).
this setting is in preferences > system
its nice to say, loop over a result set, and create a list of dictionaries
Mine and your two ALL work and return the same value of “WAL”, at least for me
Yes, I see both your version and mine would work. Thanks.
I found out that you can test what mode you are in via the following:
Code:db eval {PRAGMA journal_mode} {
echo $journal_mode
}Read more here:
Old topic I know, but for this WAL do you execute it like:
Code:db eval {PRAGMA journal_mode=WAL}
Or is it in your table creation.
In other words can you provide a more complete example?
May 16, 2017 at 11:45 am in reply to: Upgrade of Cloverleaf from 5.7 to 6.1.2 – ODBC issues?? #85106Maybe using globals and your data is getting overwritten by different threads
We are on 6.1.2 and I think we have the ssl package license. Thats not a separate install is it? We also have the web services….which is a separate install.
Right, both sides would need to be speaking the same language.
I was trying to put feelers out to see what language that was… if anyone else was doing anything like it today.
How do you set cloverleaf to use an ssl channel?
Thanks jeff, that looks like the same data, without the messiness of msi.
Russ, what you have works, i kind of wanted it to be one script, or at least have that ability.
I started looking into interp. And made it pretty far, however I still get the same with when doing an msiAttach on a subsequent site.
Code:set s [interp create]
proc hello2 {} {
puts “hello2”
}proc mykeylkeys {arg} {
return [keylkeys arg]
}
proc mykeylget {arg1 arg2} {
return [keylget arg1 $arg2]
}# Procs that they need access to
interp alias $s hello2 {} hello2
interp alias $s msiAttach {} msiAttach
interp alias $s msiDetach {} msiDetach
interp alias $s msiGetStatSample {} msiGetStatSample
interp alias $s keylkeys {} mykeylkeys
interp alias $s keylget {} mykeylget
interp alias $s echo {} echo# Variables that they need access to
interp eval $s [list “set” “threads” $threads]
interp eval $s [list “set” “auto_path” $::auto_path]
#interp eval $s [list “set” “env” $env]set threads [interp eval $s {
proc hello {} {
puts “hiya”
}
global env
#hello
#hello2
#puts $auto_path
msiAttachset idx -1
foreach thread $threads {# Get name from dictionary
set Name [dict get $thread Name]# Get stats
set result [msiGetStatSample $Name]set StatKEYS [keylkeys $result]
# Protocal Status (UP/DOWN/CONNECTING)
set Status “Unknown”
if {[lsearch -exact $StatKEYS “PSTATUS”] != -1} {
set Status [string totitle [keylget $result PSTATUS]]
}
dict append thread Status $Status
}
msiDetach
return $threads
}]interp delete $s
return the first site, but then the seoncd site gets the following error on attach
Code:[0:TEST] oilSysSemOpen: ftok failedSem Name = /NetConfig Project Id : 70[0:TEST] msiGlobalInit: Can’t open guard sem: No such file or directorymsiGlobalInit: NetConfig = /NetConfig
For now I think ill go with jeffs command
Nice. I like how you’re including /etc/.profile instead of exporting cl_install_dir. Here is my new newup variable:
Code:NEWUP=’. /etc/profile;. /home/hci/.profile’
Any news on this. Running 6.1, and while msiDetach is present, you cannot msiAttach then msiDetach, switch sites, and then msiAttach
slight tweak, i thought it was working, but it wasnt. This however is.
Code:#Define the variable with the command to execute to gain context
HCIBASE=/qdxiprod/cis6.1
NEWUP=’export CL_INSTALL_DIR=$HCIBASE;source /home/hci/.profile;’#Start of cron commands
# . COMMAND – this will run command in the current context. If you exclude this you
# will start a new shell with no context. If you use ‘exit’ while IN context it will stop the rest of the cron line from executing.#This works
#* * * * * eval $NEWUP; showroot; setsite physician1; showroot;. $HCIROOT/usercmds/setTest; showroot;
0,15,30,45 * * * * eval $NEWUP;. $HCIROOT/usercmds/intmon.sh 2>&1; -
AuthorReplies