New user - how to read the cloudi tests output files

[Bob Gustafson]

 I think I have cloudi running fine on Fedora 21.

In the /usr/local/var/log/cloudi directory, there are a number of files:

[user1@hoho8-chidig-com cloudi]$ ls -l
total 320
-rw-r--r--. 1 root root  11963 May 18 15:24 1
-rw-r--r--. 1 root root  11963 May 25 19:13 2
-rw-r--r--. 1 root root  11963 May 26 13:04 3
-rw-r--r--. 1 root root      0 May 18 15:24 cloudi.log
-rw-r--r--. 1 root root 260734 May 26 18:04 erlang.log.1
-rw-r--r--. 1 root root      1 May 26 13:04 index
-rw-r--r--. 1 root root    279 May 26 13:04 run_erl.log
-rw-r--r--. 1 root root  14677 May 26 13:04 sasl.log
[user1@hoho8-chidig-com cloudi]$

I'm guessing that the 1, 2, 3 files are output files from the tests (maybe the hexpi digits).

These files seem to be encoded with some binary characters. Is there a way to easily read these files?

Looking good so far.

Bob G

[Michael Truog]

On 05/26/2015 04:17 PM, Bob Gustafson wrote:

 I think I have cloudi running fine on Fedora 21.

In the /usr/local/var/log/cloudi directory, there are a number of files:

[user1@hoho8-chidig-com cloudi]$ ls -l
total 320
-rw-r--r--. 1 root root  11963 May 18 15:24 1
-rw-r--r--. 1 root root  11963 May 25 19:13 2
-rw-r--r--. 1 root root  11963 May 26 13:04 3
-rw-r--r--. 1 root root      0 May 18 15:24 cloudi.log
-rw-r--r--. 1 root root 260734 May 26 18:04 erlang.log.1
-rw-r--r--. 1 root root      1 May 26 13:04 index
-rw-r--r--. 1 root root    279 May 26 13:04 run_erl.log
-rw-r--r--. 1 root root  14677 May 26 13:04 sasl.log
[user1@hoho8-chidig-com cloudi]$

I'm guessing that the 1, 2, 3 files are output files from the tests (maybe the hexpi digits).

The 1,2,3 files aren't really necessary, they are useful if you want to use the Erlang report browser (http://www.erlang.org/doc/man/rb.html).  All the data in the 1,2,3 files should be present already in the erlang.log.1 file and the sasl.log file.  However, all the main output is in the cloudi.log file.

The output of the hexpi test is going to /usr/local/lib/cloudi-1.5.0/tests/http_req/public_html/hexpi.txt by going through cloudi_service_filesystem (it is using HTTP byte-range request updates to store the hexadecimal digits as they are computed).  A link to the file can be seen if you browse to http://localhost:6464/tests/http_req/ which creates CloudI service requests through cloudi_service_http_cowboy (using cowboy running on port 6464) to provide HTTP request responses.

These files seem to be encoded with some binary characters. Is there a way to easily read these files?

Looking good so far.

Bob G

--
You received this message because you are subscribed to the Google Groups "CloudI Questions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cloudi-questio...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bob Gustafson]

On 05/26/2015 06:35 PM, Michael Truog wrote:

On 05/26/2015 04:17 PM, Bob Gustafson wrote:

 I think I have cloudi running fine on Fedora 21.

In the /usr/local/var/log/cloudi directory, there are a number of files:

[user1@hoho8-chidig-com cloudi]$ ls -l
total 320
-rw-r--r--. 1 root root  11963 May 18 15:24 1
-rw-r--r--. 1 root root  11963 May 25 19:13 2
-rw-r--r--. 1 root root  11963 May 26 13:04 3
-rw-r--r--. 1 root root      0 May 18 15:24 cloudi.log
-rw-r--r--. 1 root root 260734 May 26 18:04 erlang.log.1
-rw-r--r--. 1 root root      1 May 26 13:04 index
-rw-r--r--. 1 root root    279 May 26 13:04 run_erl.log
-rw-r--r--. 1 root root  14677 May 26 13:04 sasl.log
[user1@hoho8-chidig-com cloudi]$

I'm guessing that the 1, 2, 3 files are output files from the tests (maybe the hexpi digits).

The 1,2,3 files aren't really necessary, they are useful if you want to use the Erlang report browser (http://www.erlang.org/doc/man/rb.html).  All the data in the 1,2,3 files should be present already in the erlang.log.1 file and the sasl.log file.  However, all the main output is in the cloudi.log file.

The output of the hexpi test is going to /usr/local/lib/cloudi-1.5.0/tests/http_req/public_html/hexpi.txt by going through cloudi_service_filesystem (it is using HTTP byte-range request updates to store the hexadecimal digits as they are computed).  A link to the file can be seen if you browse to http://localhost:6464/tests/http_req/ which creates CloudI service requests through cloudi_service_http_cowboy (using cowboy running on port 6464) to provide HTTP request responses.

The hexpi.txt file in tests/http_req/public_htm has only one character (a period). And the date is Apr 13 02:15

Also, when I browse for localhost:6464 or localhost:6467 (in doc), I get Connection refused.

If I do a 'netstat -nl | grep 6464, no listener shows up.

I'm just using the cloudi system as downloaded (with all the languages and tests).
Maybe I need an ACL set ? or a service ?

Thanks for your reply

Bob G

[Michael Truog]

On 05/26/2015 04:51 PM, Bob Gustafson wrote:

On 05/26/2015 06:35 PM, Michael Truog wrote:

On 05/26/2015 04:17 PM, Bob Gustafson wrote:

 I think I have cloudi running fine on Fedora 21.

In the /usr/local/var/log/cloudi directory, there are a number of files:

[user1@hoho8-chidig-com cloudi]$ ls -l
total 320
-rw-r--r--. 1 root root  11963 May 18 15:24 1
-rw-r--r--. 1 root root  11963 May 25 19:13 2
-rw-r--r--. 1 root root  11963 May 26 13:04 3
-rw-r--r--. 1 root root      0 May 18 15:24 cloudi.log
-rw-r--r--. 1 root root 260734 May 26 18:04 erlang.log.1
-rw-r--r--. 1 root root      1 May 26 13:04 index
-rw-r--r--. 1 root root    279 May 26 13:04 run_erl.log
-rw-r--r--. 1 root root  14677 May 26 13:04 sasl.log
[user1@hoho8-chidig-com cloudi]$

I'm guessing that the 1, 2, 3 files are output files from the tests (maybe the hexpi digits).

The 1,2,3 files aren't really necessary, they are useful if you want to use the Erlang report browser (http://www.erlang.org/doc/man/rb.html).  All the data in the 1,2,3 files should be present already in the erlang.log.1 file and the sasl.log file.  However, all the main output is in the cloudi.log file.

The output of the hexpi test is going to /usr/local/lib/cloudi-1.5.0/tests/http_req/public_html/hexpi.txt by going through cloudi_service_filesystem (it is using HTTP byte-range request updates to store the hexadecimal digits as they are computed).  A link to the file can be seen if you browse to http://localhost:6464/tests/http_req/ which creates CloudI service requests through cloudi_service_http_cowboy (using cowboy running on port 6464) to provide HTTP request responses.

The hexpi.txt file in tests/http_req/public_htm has only one character (a period). And the date is Apr 13 02:15

Also, when I browse for localhost:6464 or localhost:6467 (in doc), I get Connection refused.

If I do a 'netstat -nl | grep 6464, no listener shows up.

I'm just using the cloudi system as downloaded (with all the languages and tests).
Maybe I need an ACL set ? or a service ?

That stuff is only running if you have the integration tests turned on.  The integration tests can be disabled when using the configure script with the --without-integration-tests command line argument, or by having one or more of the supported programming languages disabled.  So, if the integration tests aren't running, the logs won't be as interesting and it won't be as clear whether everything is working.  You can confirm whether /usr/local/etc/cloudi/cloudi.conf has an empty list for the services entry (which means that no integration tests are being ran when CloudI is started (i.e., it is only starting the CloudI source code, so the Erlang/C++ source code is working as expected).  To see the integration test entries, you can see the configuration entries at https://github.com/CloudI/CloudI/blob/develop/src/cloudi.conf.in#L14 .  However, if you attempt to enable the integration tests, you will need to reinstall, since it has skipped the compilation of the integration tests during the initial installation (if they were disabled).

[Bob Gustafson]

That stuff is only running if you have the integration tests turned on.  The integration tests can be disabled when using the configure script with the --without-integration-tests command line argument, or by having one or more of the supported programming languages disabled.  So, if the integration tests aren't running, the logs won't be as interesting and it won't be as clear whether everything is working.  You can confirm whether /usr/local/etc/cloudi/cloudi.conf has an empty list for the services entry (which means that no integration tests are being run when CloudI is started (i.e., it is only starting the CloudI source code, so the Erlang/C++ source code is working as expected).  To see the integration test entries, you can see the configuration entries at https://github.com/CloudI/CloudI/blob/develop/src/cloudi.conf.in#L14 .  However, if you attempt to enable the integration tests, you will need to reinstall, since it has skipped the compilation of the integration tests during the initial installation (if they were disabled).

Yes, the /usr/local/etc/cloudi/cloudi.conf has all empty arrays.

Hmm, thought I recompiled everything without the '--without-integration-tests' as a configure option.

(but ANY errors in the config/make/install will do funny things.)

-----

OK, it is working now. I did a massive 'make clean' by wiping everything except the tar.gz and then untared again.
There are also cloudI things in /usr/local/bin, lib, var/log, lib which I also got rid of (may not have had to)

The problem was that configure could not find uuid/uuid.h

   sudo dnf install uuid-devel ef2sprogs-devel libuuid-devel

took care of that problem (running on Fedora 22)  (I think it was the libuuid-devel that did the trick)

Then recompiled and re-installed, cloudi is working fine.

The /usr/local/etc/cloudi/cloudi.conf file has 1156 lines instead of only 1

----

I see 65537 hex pi digits in /usr/local/lib/cloudi-1.5.0/tests/http_req/public_html/hexpi.txt

The http://localhost:6464/tests/http_req/           looks good. Julia set could be in color though :-)

Thanks much - I have a lot more reading to do now.

Bob G