by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Bahadir
@bwh
@albogdano is there any way to debug the LDAP parameters being sent? I receive an error 400 on the console, "check if the user is active", but I can't see which string is being sent as user?
Alex Bogdanovski
@albogdano
@bwh you can start Para with the system property -Dlogging.level.org.springframework=DEBUG
actually it's -Dlogging.level.org.springframework=DEBUG
Bahadir
@bwh
thanks for the quick response
Alex Bogdanovski
@albogdano
actually I might be wrong... let me check that
Alex Bogdanovski
@albogdano
so, yes, -Dlogging.level.org.springframework.ldap=DEBUG should print out LDAP debug info if added to the Para command line: java -jar -Dlogging.level.org.springframework.ldap=DEBUG para.jar
Bahadir
@bwh
yeah, I've realized that I should add the -D parameter between java and the para.jar :)
I searched for a long time to find the log file, than realized the command line structure and saw them on the terminal :)
sujai1009
@sujai1009
hi all, i am new to para, i made a build from the source, if i try to run with my custom application.conf... mvn spring boot command is not picking up
mvn -Dconfig.file=./application.conf spring-boot:run
Alex Bogdanovski
@albogdano
@sujai1009 try mvn spring-boot:run -Dconfig.file=./application.conf
sujai1009
@sujai1009
thank you @albogdano still the same.
for test purpose i changed para.env = "2" in my custom file. but para server starts in Para.initialize() [production]
Alex Bogdanovski
@albogdano
well, try para.env = "embedded" instead of 2
sujai1009
@sujai1009
ok sure. Still the same
Alex Bogdanovski
@albogdano
mvn spring-boot:run -Dspring-boot.run.jvmArguments="-Dconfig.file=./application.conf"
sujai1009
@sujai1009
bingo. it worked . Thank you so much @albogdano
Alex Bogdanovski
@albogdano
:thumbsup:
sujai1009
@sujai1009
i was struggling with this for past 2 hours
sujai1009
@sujai1009
Thanks again @albogdano
prog20901
@prog20901
How to generate java doc as PDF file ? Open source software and tools ???
Danilo Souza
@danxsouza_twitter

Hi Alex
Can you help me, I can't figure out the reason for this error?

[ERROR] 400 - User belongs to an app that does not exist.

Alex Bogdanovski
@albogdano
@danxsouza_twitter did you initialize Para with GET /v1/_setup
1 reply
Alex Bogdanovski
@albogdano
@danxsouza_twitter Are you sure you created the new app kaffa or you just used the secret key of the root app app:para and changed its name to app:kaffa? Also remove the app_secret_key value fro your Para configuration. That should be a random secret not equal to the secret for app:kaffa.
1 reply
Also check if data is actually saved to disk. What happens if you open GET /v1/_setup again? does it say "all set!"?
Alex Horn
@HorncaAlex_twitter
Hi Alex
Alex Horn
@HorncaAlex_twitter
Thanks for posting "Building a full stack application from scratch with Angular" on your blog. While following your directions I have successfully built the application using Para as the back-end. The issue I'm running into is that although both the para console and angular say my application is running the browser isn't rendering the site. All I'm seeing is;
{
"totalHits" : 0,
"page" : 0,
"items" : [ ]
}
Alex Bogdanovski
@albogdano
@HorncaAlex_twitter I can't really tell what the actual problem is in your case. Check your Angular controller code and the model data in particular
Afshin Mortazavi-Nia
@amortaza
Hi. Just installed para and following the "Quick Start" steps. But I am seeing some unexpected behavior.
I am on Ubuntu 20.04, I ran curl localhost:8080/v1/_setup
The para jar is running so everything is good so far.
I ran para-cli setup and entered the access key and secret key and http://localhost:8080 is set as the endpoint.
The output of para-cli setup is that New JWT generated... however Connection failed. Run "para cli-setup" or check the configuration file...
I check the configuration file and everything looks good.
Afshin Mortazavi-Nia
@amortaza
I try running para-cli new-app "myapp" --name "My App" and get the Connection failed. Run "para cli-setup" or check the configuration file... message.
So I fiddle around with the config.json file and append / to the endpoint (ie http://localhost:8080/).
Now when I run the new-app command, it tells me the app already exists. So I try the new-app again with an app name I have never used before random33 and it tells me the app already exists. What!??
Is the endpoint supposed to end with / ?
and if so, why does it tell me an app already exists whenever I try to create it?
Afshin Mortazavi-Nia
@amortaza
After restarting the para jar server, now I get Only root app can create and initialize other apps when I use an endpoint in the config.json file that doesn't end in /.
I hope that isn't too confusing.
I appreciate any help
Alex Bogdanovski
@albogdano
@amortaza I think the Para CLI fails to connect because your Para server is not allowing clients to connect to the root app. Can you check that you have para.clients_can_access_root_app = true?
Afshin Mortazavi-Nia
@amortaza

@albogdano Yes, that property is set to true

para.app_name = "Para"
para.env = "embedded"
para.security.allow_unverified_emails = true
para.clients_can_access_root_app = true
para.cache_enabled = true
para.app_secret_key = "b8db69a24a43f2ce134909f164a45263"
para.security.api_security = false
para.worker_id = 1

Here is the content of ~/.config/para-cli-nodejs/config.json
{
"accessKey": "app:para",
"secretKey": "mMEzD6pTGhqbt8n4n3UMTBl1dH9dWTsK6KDThiDFyeLJLzrnRKXCug==",
"endpoint": "http://localhost:8080",
"jwt": "eyJhbGciOiJIUzI1NiJ9.eyJleHAiOjE1OTUwNTA4OTUsImlhdCI6MTU5NDQ0NjA5NSwibmJmIjox>
}

Afshin Mortazavi-Nia
@amortaza

@albogdano

Here is the output of para jar on startup (notice it says 0 existing child apps)

2020-07-11 09:25:19 [INFO ] --- Para.initialize() [embedded] ---
2020-07-11 09:25:19 [INFO ] Loaded new DAO, Search and Cache implementations - H2DAO, LuceneSearch and CaffeineCache.
2020-07-11 09:25:19 [INFO ] Server is healthy.
2020-07-11 09:25:19 [INFO ] Found root app 'para' and 0 existing child app(s).
2020-07-11 09:25:19 [INFO ] Instance #1 initialized.
2020-07-11 09:25:20 [INFO ] Starting ParaServer on ace-ubuntu with PID 4805 (/home/ace/projects/java/para/para-jar-1.37.0.jar started by ace in /home/ace/projects/java/para)
2020-07-11 09:25:20 [INFO ] The following profiles are active: embedded
2020-07-11 09:25:20 [INFO ] Listening on port 8080...
2020-07-11 09:25:21 [INFO ] Started ParaServer in 1.443 seconds (JVM running for 3.222)

Alex Bogdanovski
@albogdano
@amortaza the issue here is caused by para.security.api_security = false. set this back to true while I fix this inconsistent behavior, when API security is disabled
Afshin Mortazavi-Nia
@amortaza
@albogdano Thank you, sir. Lesson learned - don't fudge with parameters you don't understand!