Logiweb(TM)     Logiweb online help  
        Servers  
 

System pages
Site pages

Introduction...
Showroom
Tutorials
Man pages
Help
Download
Wiki...
Wiki submission
Background
Machine room...
Contact

Overview
Browser
Compiler
Server
Misceleneous

Server States
User Interface
HTTP Interface

   

Home. Help index. Logiweb server states. Logiweb protocol. Relay interface. Relay url syntax.

Introduction

Logiweb servers work behind the scenes, maintaining a catalog of all Logiweb pages. Logiweb servers provide the service to translate Logiweb references to Uniform Resource Locators (URLs).

Each server maintains a Logiweb server state. All server states of all Logiweb servers collectively represent the catalog of all Logiweb pages.

Logiweb servers communicate with their clients and each other using the Logiweb protocol.

Logiweb relays allow humans to interact with a Logiweb server using a web browser. The relay is intended for implementers of Logiweb servers and Logiweb clients who want to play with the system to see how it is supposed to react.

As an example, you may find a Logiweb relay here.

Logiweb relay errors

If you see a web page saying 'Logiweb relay error ...' then contact the webmaster of the site in question. If you are the web master, you may find the following useful:

connect( ) failed, Connection refused
This typically means that the Logiweb server is dead or that it listens on some other socket than the CGI-relay expects. To check the former, issue a command like '/sbin/service logiweb status' or lgwping. To check the latter, locate the CGI-script (e.g. in /var/www/logiweb/relay), read the CGI-script (it typically says something like '/usr/local/bin/lgwrelay 127.0.0.1 65535 ...'). Then check that the tcphost and tcpport parameters are set to similar values in the Logiweb configurations files. As a quick test, try to issue 'pyk optionstr=tcphost' and 'pyk optionstr=tcpport' to see where the pyk compiler thinks the server listens.
socket( ) failed, Permission denied
This typically means that CGI-scripts are not allowed to connect to the network. As an example, on Fedora, one may run system-config-securitylevel, click on SELinux, click on 'HTTPD Service', and check 'Allow HTTPD scripts to connect to the network'. To see if the Permission denied problem is connected to CGI-scripts, try running 'lgwrelay 127.0.0.1 2 3 4 5' from a user shell. If that gives a 'connect( ) failed, Connection refused' instead of a 'socket( ) failed, Permission denied' then the problem is with CGI-scripts.