From: Laurent L. <Lau...@un...> - 2021-05-26 15:41:26
|
Hi Bernard, > On 26 May 2021, at 16:44, Bernard Desgraupes <bde...@or...> wrote: > > Hi Laurent, > > thank you for reporting this. I don’t know what’s going on there. > > Is it possible that the port used by the AlphaServer (51954) is already in use on your machine ? Any idea how I could check that? > > To help me debug, could you execute the following two commands from the Tcl shell (cmd-Y) once Alpha is running after this activation error: > > alphaServer::port > alphaServer::isRunning > > > Here is for instance what I get on my machine: > Welcome to Alpha's AlphaTcl shell. > «» alphaServer::port > 51954 I get 59218. The default value of 51954 is detected in several files when I run from a terminal « grep -r 51954 /Applications/Alpha.app ». But for some reason, it apparently looks interpreted as busy and another port number is (randomly) chosen. > «» alphaServer::isRunning > 1 I get 1 > «» set alphaServer::serverAddress > 127.0.0.1 I get 127.0.0.1 To further document the behaviour of the error message window: the « OK » button is initially displayed in blue and I need to click it, changing its aspect to un-coloured transparent, before I can use Alpha. The error message window does not disappear however: it remains with the un-coloured « OK » button. And I « need to search » the new windows that I open in Alpha: command-N results in an Alpha status line message indicating « untitled 'command symbol’1, but the new window is nowhere to be seen first. A sure way to make it appear is for instance to start a search by command-F. Thank you for your reactivity! Laurent > > Bernard > > >> Le 26 mai 2021 à 15:04, Laurent Lamalle <Lau...@un... <mailto:Lau...@un...>> a écrit : >> >> Hello, >> >> I systematically get an error message when starting Alpha, and this has been observed over quite a few latest versions: >> >> Package activation error >> >> The package ‘alphaServer’ will be deactivated if >> possible. See the log file ‘…/Library/Logs/AlphaTcl/ActivationError’. >> >> The window presenting this message displays an « OK » button, but clicking the latter has no effect. >> The window remains open but does not prevent using Alpha. >> >> The mentioned log file indicates: >> >> ---------------------------------------------------------------------- >> Wed May 26 14:38:48 CEST 2021 >> couldn't open socket: nodename nor servname provided, or not known >> while executing >> "socket localhost $serverPort" >> (procedure "::alphaServer::start" line 32) >> invoked from within >> "::alphaServer::start" >> ("uplevel" body line 3) >> invoked from within >> "uplevel #0 { >> # Activation script. >> ::alphaServer::start >> }" >> >> Currently, the earliest occurrence of this error snippet in my log file dates back August 2020, but it is possible I thrashed the file at that time to try understanding what happened, and the problem is likely more ancient. >> >> I did not notice this problem when switching to early AlphaCocoa versions, as far as I remember, and have no idea what could have triggered this behaviour. >> >> I am using macOS HighSierra 10.13.6. >> I just updated to the latest Alpha version. >> >> Any idea? >> >> Thank you in advance for your help. >> >> Best regards, >> >> Laurent Lamalle >> >> >> -- >> Laurent LAMALLE >> Ingénieur de Recherche INSERM >> >> Inserm US 17 >> CNRS UMS 3552 >> Université Grenoble Alpes & CHU Grenoble Alpes UMS IRMaGe >> >> RMN biomédicale et Neurosciences, SFR de l'Université Grenoble Alpes >> >> Unité IRM 3T - Recherche >> CHU de Grenoble >> CS 10217 >> 38043 Grenoble Cedex 9 >> France >> >> Tel : +33 (0)4 76 76 93 07 >> Fax: +33 (0)4 76 76 93 05 >> mailto: Lau...@un... <mailto:Lau...@un...> >> mailto: Lau...@in... <mailto:Lau...@in...> >> https://irmage.univ-grenoble-alpes.fr <https://irmage.univ-grenoble-alpes.fr/> >> _______________________________________________ >> AlphaCocoa-devel mailing list >> Alp...@li... <mailto:Alp...@li...> >> https://lists.sourceforge.net/lists/listinfo/alphacocoa-devel > |