 atesetup (auto-update-detection) problem
#30830
22 May 14 10:17 AM
|
Joined: Jun 2001
Posts: 11,794
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,794 |
Originally posted by Frank - edgeMED Healthcare (in another unrelated thread):Unrelated but related: I loaded this new version into the atesetup on my directory on my inhouse server and my current version 1384.3 is not asking if i want to upload this new version. It was working for me at one point... what is the trigger for this? Does ATE automatically look here upon launch? [root@Zoom atesetup]# pwd
/vm/miame/atesetup
[root@Zoom atesetup]# ls -al
total 624
drwxrwxr-x 2 zoom fmc 4096 May 22 10:24 .
drwxrwxrwx 66 fmc fmc 12288 May 21 17:02 ..
-rwxr--r-- 1 user fmc 303112 May 22 2014 ate-6.1.1385.1-edgeMED.exe
-rwxr--r-- 1 user fmc 306 May 7 15:54 ate.txt
-rw-r--r-- 1 support frank 143360 Apr 23 2007 ICSharpCode.SharpZipLib.dll
-rw-r--r-- 1 support frank 122880 Apr 23 2007 UpdateCenter.exe
-rw-r--r-- 1 support frank 70 Apr 23 2007 UpdateCenter.ini
[root@Zoom atesetup]# [/QUOTE]
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30831
22 May 14 10:21 AM
|
Joined: Jun 2001
Posts: 11,794
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,794 |
In theory ashell scans the %MIAME%/atesetup directory looking for files of the form ate-#.#.####.#{optional suffix}.exe and then compares the #.#.####.# with the version currently executing on the client. So offhand I don't see a problem, but fortunately there are some built-in traces which can help.
Add TRACE=ATE to the server-side miame.ini and try connecting again, then take a look at the ashlog.log entries, starting with a line containing Checking atesetup dir for ATE update:
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30832
22 May 14 12:58 PM
|
Joined: Sep 2002
Posts: 5,471
Frank
Member
|
|
Member
Joined: Sep 2002
Posts: 5,471 |
Ok this is what I get. I must be doing something different or wrong all of a sudden because on my last update this worked fine: 22-May-14 12:42:38 [p31658-0]<:0> ----------------
22-May-14 12:42:38 [p31658-0]<:0> A-Shell 6.1.1374.0 launched on pts/14:31658 by zoom
22-May-14 12:42:38 [p31658-0]<:0> gui_flags = 0
22-May-14 12:42:38 [p31658-0]<:0> TAB(-10,6) (tputch)
22-May-14 12:42:38 [p31658-0]<:0> TAB(-10,7) (tputch)
22-May-14 12:42:38 [p31658-0]<ASTART:0> gui_flags2 = a4, m0.ztver = , tdv = AM75G
22-May-14 12:42:38 [p31658-0]<ASTART:0> TAB(-10,16) (tputch)
22-May-14 12:42:38 [p31658-0]<ASTART:0> -> xtab(-10,85) 1,222
22-May-14 12:42:38 [p31658-0]<ASTART:0> TAB(-10,85) (tputch)
22-May-14 12:42:38 [p31658-0]<ASTART:0> Creating ate response buffer (3072 bytes)
22-May-14 12:42:38 [p31658-0]<ASTART:0> <- ate_response(kbd)=Þ, count=1, *filter=0, ctrlt=0
22-May-14 12:42:38 [p31658-0]<ASTART:0> <- stray typeahead buf: go80^M (5 chars)
22-May-14 12:42:38 [p31658-0]<ASTART:0> -> xtab(-10,95) go80
22-May-14 12:42:38 [p31658-0]<ASTART:0> TAB(-10,95) (tputch)
22-May-14 12:42:38 [p31658-0]<ASTART:0> -> xtab(-10,85) 2,6,1,1374,0,0,0,"Edgemed^M",4028QBEL-5690-BFZ-7908DC-YXFGAFM1,0,0,0
22-May-14 12:42:38 [p31658-0]<ASTART:0> TAB(-10,85) (tputch)
22-May-14 12:42:38 [p31658-0]<ASTART:0> <- ate_response(kbd)=6,0,1261,100663296,4,1449434,192,168,1,3,64,31,50,3c,b3,e3,4028QB..., c
22-May-14 12:42:38 [p31658-0]<ASTART:0> atelicack: 055e
22-May-14 12:42:38 [p31658-0]<ASTART:0> Checking atesetup dir for ATE update: /vm/miame/atesetup/
22-May-14 12:42:38 [p31658-10]<ASTART:0> ATE Server License Issued
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30833
22 May 14 01:06 PM
|
Joined: Jun 2001
Posts: 11,794
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,794 |
The "checking atesetup..." message appears before it tries to find the atesetup directory, and assuming it finds it, it would log every file that starts with "ate-", so my best guess is that it can't find/access the atesetup directory, perhaps because of the privilege settings?
Let's see an ls -l of the /vm/miame directory.
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30834
22 May 14 01:37 PM
|
Joined: Sep 2002
Posts: 5,471
Frank
Member
|
|
Member
Joined: Sep 2002
Posts: 5,471 |
Aye Cap - I presume this is what your looking for:
rwxrwxrwx 1 fmc fmc 20108 Dec 11 2007 ashlog.bak
-rw-rw-rw- 1 fmc root 1666935 May 22 14:22 ashlog.log
drwxrwxr-x 2 zoom fmc 4096 May 22 10:24 atesetup
-rwxrwxrwx 1 fmc fmc 364 Oct 19 2007 .bash_profile
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30835
22 May 14 03:50 PM
|
Joined: Jun 2001
Posts: 11,794
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,794 |
Looks fine; I'm stumped. I guess I would try putting a dummy file, like ate-1.2.3.4.exe there to see if it shows up in the log (which might help clarify if the problem is in the FINDFIRST operation to find the /vm/miame/atesetup directory, or in the FINDNEXT (which is used to examine each file in the directory).
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30836
22 May 14 04:01 PM
|
Joined: Jun 2001
Posts: 11,794
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,794 |
FYI, I tried adding several variations of ate-#.#.#.# files in your test server /vm/miame/atesetup and they all show up in the log, so there is apparently something mysterious about that one file. I even made a copy of it with a new name and the new copy shows up, so maybe that's all you need to do.
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30837
22 May 14 04:02 PM
|
Joined: Sep 2002
Posts: 5,471
Frank
Member
|
|
Member
Joined: Sep 2002
Posts: 5,471 |
Interesting not its seeing the -1000 version and asking about that one... something wrong with the 1385 flavor I dropped in there? 22-May-14 16:46:08 [p5846-0] Checking atesetup dir for ATE update: /vm/miame/atesetup/
22-May-14 16:46:08 [p5846-0] atesetup/ate-6.1.1000.9-edgeMED.exe
22-May-14 16:46:08 [p5846-0] atesetup/ate-1.2.3.4-jack.exe
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30838
22 May 14 04:03 PM
|
Joined: Sep 2002
Posts: 5,471
Frank
Member
|
|
Member
Joined: Sep 2002
Posts: 5,471 |
ha - just crossed posts - indeed.
I had zipped that up into ate.zip and then unzipped it in that directory. I wonder if that changed anything...
weird goosechase - sorry
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30839
24 Jul 19 09:32 AM
|
Joined: Nov 2006
Posts: 2,223
Stephen Funkhouser
Member
|
|
Member
Joined: Nov 2006
Posts: 2,223 |
We're experiencing a version update detection issue. [root@vmware-kk-vagrant ~]# ls -l /var/data/kkvet/ashell/vm/miame/atesetup
total 25960
-rwxrwx--- 1 ashusr ashell 253808 Jul 3 08:19 ate-6.5.1660.7-web.exe
-rwxrwx--- 1 ashusr ashell 26328080 Jul 24 09:18 ate-6.5.1663.1.exe The -web suffix is taking precedence (i.e. 1660.7), and our users are having to update twice. If I rename 1663.1 with the -web suffix the version detection works. The message is New ATE Version 6.5.1663.1 (web) It also detects the correct version when I remove -web from both files. The message is New ATE Version 6.5.1663.1. Probably just a substring suffix regex problem. Just wanted to make sure this was known. P.S. I'll probably change the files to have a -web just so we can be sure only one update is needed.
Stephen Funkhouser
Diversified Data Solutions
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30840
24 Jul 19 10:09 AM
|
Joined: Jun 2001
Posts: 11,794
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,794 |
Thanks for the report - I'll figure that out and resolve it in the next patch.
|
|
|
|
Re: atesetup (auto-update-detection) problem
#30841
24 Jul 19 11:19 PM
|
Joined: Jun 2001
Posts: 11,794
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,794 |
I think the issue here was a questionable decision to favor the -web version in all cases where there were both -web and non-web versions available. I changed that in the latest update to favor the version with the highest version number. ... ash65notes.txt ash-6.5.1664.0-el5-upd.tz ash-6.5.1664.0-el7-upd.tz
|
|
|
|
|
