-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MVP#1 Application Server installation issues/observations #39
Comments
The missing module is odd, it looks like the OpenAPI bindings were not created. The build backend collects a dependencies list before it creates the distribution tar file. I suspect the I'll do some investigating and see if what I suspect is true. |
The application server should create any missing folders it sees from its configuration. But obviously can't if it doesn't have permission to do so. The defaults are set assuming the script will be run as root for a proper system service. Using an alternative configuration pointing to directories that the user can create/modify allows this to be run as an unprivileged user. |
Issues related to the Documentation (when Running)generate_openapi should be generate_5gms_as_openapi"generate_openapi" should be renamed to "generate_5gms_as_openapi" in section "Running the example without building" of /docs/README.md config file moved from /docs to /external../docs/rt-common-shared/5gms/examples/ContentHostingConfiguration_Big-Buck-Bunny_pull-ingest.json |
Issues when Running'regex' not foundIn the last step to run the example, I obtain a "ModuleNotFoundError: No module named 'regex'". It may be related to a problem finding the path but I'm not sure at the moment how to fix it
|
I'm not sure why you are getting the import error, but judging from the output quoted above I have a couple of possible reasons:
|
David, thank you for checking. Actually I could finally fix it with Regarding the 3 vs 3.8 I checked that it doesn't seem to make a difference and it is all executed correctly from the 3.8 folder. |
With the exception of the MacOS report, I think all problems have been solved, so now it's just a case of updating documentation, right, @davidjwbbc? |
Anything more to be done on this issue @davidjwbbc? Can we link it to documentation update PR(s) before closing? |
Hello, my issues have been resolved in the latest updates (all running on Ubuntu). For the issues raised by @dsilhavy, we may need to check with him, though I think the documentation regarding the ports was updated |
I'm trying to redo the rt-5gms-application-server from scratch to check the development branch. I'm getting "bad substitution" after Regenerating the 5G API bindings
|
I used "#! /bin/bash" instead of "#! /bin/sh" and it run |
I'm stuck with (apparently) the Nginx configurations. If I manually change the port of the nginx default to 8080 and do systemctl restart nginx, then I can run rt_5gms_as.app |
After a while I got a success.
|
By default the 5GMS Application server will try to use port 80 for HTTP and port 443 for HTTPS. If you have the nginx service running, it too will use port 80 or 443 by default. Therefore one of these will need to move and personally, since the 5GMS Application Server is under test I'd change that one. The 5GMS Application Server default ports can be can be easily changed by setting the appropriate values in the configuration file, for example: [5gms_as]
http_port = 8080
https_port = 8443 These can either be set in the default configuration file ( ### Defaults for the 5G-MAG Reference Tools: 5GMS applications
[DEFAULT]
log_dir = /tmp/rt-5gms-as/logs
run_dir = /tmp/rt-5gms-as
### 5GMS Application Server specific configurations
[5gms_as]
log_level = debug
cache_dir = /tmp/rt-5gms-as/cache
certificates_cache = /tmp/rt-5gms-as/certificates
http_port = 8080
https_port = 8443
#access_log = %(log_dir)s/application-server-access.log
#error_log = %(log_dir)s/application-server-error.log
#pid_path = %(run_dir)s/application-server.pid
### 5GMS Application Server nginx specific configuration
[5gms_as.nginx]
#root_temp = /var/cache/rt-5gms/as
root_temp = /tmp/rt-5gms-as
#client_body_temp = %(root_temp)s/client-body-tmp
#proxy_temp = %(root_temp)s/proxy-tmp
#fastcgi_temp = %(root_temp)s/fastcgi-tmp
#uwsgi_temp = %(root_temp)s/uwsgi-tmp
#scgi_temp = %(root_temp)s/scgi-tmp
#pid_path = %(root_temp)s/5gms-as-nginx.pid ...and use
That is strange, as though it got part way through deploying, but never replied to the M3 client. It's difficult to know what's going on there, I've not seen that before. |
Will check.
I'm going to create the local-dev version |
I've checked the entire AS instructions. All seems to work subject to:
|
I've got a fix pending for the first one of those. The second is a documentation update, however most of those should automatically get installed when you do The |
David, |
Hello, I can confirm that in Ubuntu 22.04.1 the OpenSSL is version 3. When building the AS I get the following:
Is that UNKNOWN something to worry about? I'm unable to execute |
This has been solved by:
|
I've opened a new issue (#57) related to the MVP#2 testing (which I'm doing with AS "development" and AF "1.0.1-rc"). The error I'm getting is happening always. I've just launched |
This ticket is meant to collect issues and observations that occurred during the installation of the Application Server
Installation on MacOS Monterey Version 12.5.1
Missing module
Following the installation guide I ran into the following error when running
5gms-application-server -h
:Installation on Linux Ubuntu 20.04
Missing folders
Strictly following the installation guide I ran into a problem of missing folders. The following commands are required to create the folders:
Nginx port bindings
Binding to port
80
is only possible with root privileges. Running5gms-application-server external/rt-common-shared/5gms/examples/ContentHostingConfiguration_Big-Buck-Bunny_pull-ingest.json
lead to anginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)
error.This can be solved by following the instructions in the development documentation and creating an adjusted configuration using other ports:
The new config can be provided via
5gms-application-server -c custom-application-server.conf external/rt-common-shared/5gms/examples/ContentHostingConfiguration_Big-Buck-Bunny_pull-ingest.json
Afterwards the sample MPD is available at
http://localhost:8080/m4d/provisioning-session-d54a1fcc-d411-4e32-807b-2c60dbaeaf5f/BigBuckBunny_4s_onDemand_2014_05_09.mpd
The text was updated successfully, but these errors were encountered: