-
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#2 Application Server installation/running issues/observations #57
Comments
The AS runs independently of the AF in MVP#2, so it should be possible to start them in any order. |
The error you posted indicates that the AS is having trouble creating a directory:
Looks like the process lacks permissions to create the directory Does that directory already exist in your system, but is owned by root while you are trying to run the AS as a non-root user? |
It looks like it doesn't exist so it's actually not an issue of permission to access to it? Which process creates it? |
Reading the full error trace bottom to top suggests that the problem was encountered during a directory creation operation. If the directory doesn't exist, that suggests that that AS process lacks sufficient permission to create it. That's as far as I can help you. @davidjwbbc can take over from here! |
Thank you Richard!
|
I've tried with another machine. What I've found now is the following problem:
|
So the The The permissions issue with [DEFAULT]
log_dir = /tmp/rt-5gms-as/logs
run_dir = /tmp/rt-5gms-as
[5gms_as]
cache_dir = /tmp/rt-5gms-as/cache
certificates_cache = /tmp/rt-5gms-as/certificates
http_port = 8080
https_port = 8443
[5gms_as.nginx]
root_temp = /tmp/rt-5gms-as then run the application server as The default configuration assumes that the application server is being installed by root as a system service, so you'll need to create an alternative configuration if you wish to run as a normal user. The default configuration file can be found in |
Thank you, David. On the other PC this works:
There is no msaf.yaml in that directory. |
I copied it manually from the |
The AS shows me:
The AF shows me (based on the yaml I copied from one folder to another):
However I dont see its getting configured, it doesnt give me the ID. The server is up and running as I can see |
The development branch of the AS (v1.1.0) will work with the development branch of the AF (v1.1.0) as they both implement the M3 interface. The development AS (v1.1.0) will not get configured by the AF 1.0.1-rc as that AF does not implement M3. If you wish to test the ServiceAccessInformation returned from AF 1.0.1-rc then please use the AS release 1.0.1 (or v1.0.x branch) with the same ContentHostingConfiguration configured, as these versions are compatible with each other. The ProvisioningSessionId is set in the msaf.yaml file and will be |
I'm testing AF (development brach) and AS (1.0.1-rc). I've deleted all repos and re-started from scratch. The AF is up and running. When trying to run the AS after having installed it I got:
Not sure if my issue is now even more fundamental as the AS fails to run entirely before launching the AF. I launch the AS as
5gms-application-server
(ie without a -c configfile). What is the AS doing when no config file is specified? For MVP#2 I understand it should wait for receiving info from the AF?The text was updated successfully, but these errors were encountered: