zappy1 and zappy2 are a hangover from a time when we were running two zappy instances on a single server (long story...), just use zappy1 for everything.<br><br>Yes there are hard coded paths, the whole thing needs packaging properly. You may find it easier to work with these paths rather than trying to edit everything.<br>
<br>80n<br><br><div class="gmail_quote">On Fri, Jun 19, 2009 at 1:41 PM, Christian Lange <span dir="ltr"><<a href="mailto:clange@nw7.de">clange@nw7.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
what is the different between zappy1 zappy2 zappy4?<br>
<br>
there are many hardcoded path's in the source like "/home/etienne/...".<br>
<div><div></div><div class="h5"><br>
<br>
regards christian<br>
<br>
80n schrieb:<br>
> Christian<br>
> These are compilation errors, but actually for modules that only apply to<br>
> other platforms so they can be safely ignored.<br>
><br>
> If you re-run the process (zappy1_up I assume) you shouldn't see these<br>
> errors again.<br>
><br>
> 80n<br>
><br>
> On Fri, Jun 19, 2009 at 9:47 AM, Christian Lange <<a href="mailto:clange@nw7.de">clange@nw7.de</a>> wrote:<br>
><br>
><br>
>> Next problem is:<br>
>> o socket:(:port:"PSTA"):10 e d logMessage("Cannot open<br>
>> socket",0,port) s stop=1 q<br>
>> ^-----<br>
>> At column 12, line 53, source module serverLink.m<br>
>> %GTM-E-DEVPARUNK, Deviceparameter unknown<br>
>> . u socket:"PSTA"<br>
>> ^-----<br>
>> At column 13, line 57, source module serverLink.m<br>
>> %GTM-E-DEVPARUNK, Deviceparameter unknown<br>
>> . j<br>
>> sub01^serverLink(port,logLevel):(:4:socket:socket):10 e d<br>
>> logMessage("Cannot spawn sub-process",1,port) q<br>
>> ^-----<br>
>> At column 39, line 60, source module serverLink.m<br>
>> %GTM-E-JOBPARUNK, Job parameter unknown<br>
>> o device:("TCP":"":port):10 e d logMessage("Cannot open<br>
>> socket",0,port) s stop=1 q<br>
>> ^-----<br>
>> At column 12, line 73, source module serverLink.m<br>
>> %GTM-E-DEVPARUNK, Deviceparameter unknown<br>
>> . s socket=$zsocket(device)<br>
>> ^-----<br>
>> At column 14, line 80, source module serverLink.m<br>
>> %GTM-E-INVFCN, Invalid function name<br>
>> . u device:(::::::socket) ; Detach socket<br>
>> ^-----<br>
>> At column 14, line 82, source module serverLink.m<br>
>> %GTM-E-DEVPARUNK, Deviceparameter unknown<br>
>> . c device:socket<br>
>> ^-----<br>
>> At column 19, line 84, source module serverLink.m<br>
>> %GTM-E-DEVPARVALREQ, A value is required for this device parameter<br>
>> s $et="i $estack=0 znspace """_$znspace_""" g<br>
>> error^serverLink"<br>
>> ^-----<br>
>> At column 34, line 182, source module serverLink.m<br>
>> %GTM-E-INVSVN, Invalid special variable name<br>
>> u socket:(::"STP")<br>
>> ^-----<br>
>> At column 12, line 188, source module serverLink.m<br>
>> %GTM-E-DEVPARUNK, Deviceparameter unknown<br>
>> . u socket:(::"STP")<br>
>> ^-----<br>
>> At column 14, line 198, source module serverLink.m<br>
>> %GTM-E-DEVPARUNK, Deviceparameter unknown<br>
>> s ucivol=$zu(0)<br>
>> ^-----<br>
>> At column 12, line 228, source module serverLink.m<br>
>> %GTM-E-INVFCN, Invalid function name<br>
>> s ucivolno=$zu(uci,vol)<br>
>> ^-----<br>
>> At column 14, line 231, source module serverLink.m<br>
>> %GTM-E-INVFCN, Invalid function name<br>
>> o device:("TCP":""::::socket) ; Attach socket<br>
>> ^-----<br>
>> At column 12, line 239, source module serverLink.m<br>
>> %GTM-E-DEVPARUNK, Deviceparameter unknown<br>
>> u device:(:::$c(10))<br>
>> ^-----<br>
>> At column 12, line 285, source module serverLink.m<br>
>> %GTM-E-DEVPARUNK, Deviceparameter unknown<br>
>><br>
>><br>
>> regards christian<br>
>><br>
>> 80n schrieb:<br>
>><br>
>>> Christian<br>
>>> This can occur if you are running SELinux. In that case try it with<br>
>>><br>
>> SELinux<br>
>><br>
>>> disabled, or follow the suggestions from this post:<br>
>>><br>
>>><br>
>> <a href="http://www.mail-archive.com/hardhats-members@lists.sourceforge.net/msg16471.html" target="_blank">http://www.mail-archive.com/hardhats-members@lists.sourceforge.net/msg16471.html</a><br>
>><br>
>>> A second possibility is if you are using an AMD processor then you need<br>
>>><br>
>> to<br>
>><br>
>>> add noexec32=off to your kernel boot command line.<br>
>>><br>
>>> 80n<br>
>>><br>
>>> On Thu, Jun 18, 2009 at 11:12 AM, Christian Lange <<a href="mailto:clange@nw7.de">clange@nw7.de</a>> wrote:<br>
>>><br>
>>><br>
>>><br>
>>>> Hi,<br>
>>>> i will be setup a xapi server.<br>
>>>><br>
>>>> i have looked in <a href="http://xapi.openstreetmap.org/" target="_blank">http://xapi.openstreetmap.org/</a> and<br>
>>>> <a href="http://xapi.openstreetmap.org/scripts" target="_blank">http://xapi.openstreetmap.org/scripts</a> <scripts> .<br>
>>>><br>
>>>> but i do nothing know about GT.M<br>
>>>><br>
>>>> i have try to start zappy:<br>
>>>><br>
>>>> %GTM-F-KILLBYSIGSINFO1, GT.M process 20929 has been killed by a signal<br>
>>>> 11 at address 0xF7CFBF83 (vaddr 0x00000000)<br>
>>>> %GTM-F-SIGMAPERR, Signal was caused by an address not mapped to an<br>
>>>><br>
>> object<br>
>><br>
>>>> can anybody help me plz?<br>
>>>><br>
>>>><br>
>>>><br>
>>>> sorry for my english ;)<br>
>>>><br>
>>>><br>
>>>> regards Christian<br>
>>>><br>
>>>> _______________________________________________<br>
>>>> dev mailing list<br>
>>>> <a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a><br>
>>>> <a href="http://lists.openstreetmap.org/listinfo/dev" target="_blank">http://lists.openstreetmap.org/listinfo/dev</a><br>
>>>><br>
>>>><br>
>>>><br>
>>><br>
>> _______________________________________________<br>
>> dev mailing list<br>
>> <a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a><br>
>> <a href="http://lists.openstreetmap.org/listinfo/dev" target="_blank">http://lists.openstreetmap.org/listinfo/dev</a><br>
>><br>
>><br>
><br>
><br>
<br>
</div></div></blockquote></div><br>