NEM Beta 0.4.48

Releases
#15

@rockethead: what do you mean with "use localhost:7890"? Use in what way? To make requests in the browser?
Same question for the other port.


Yes, to make request in the browser.

http://localhost:7890 gives error
http://localhost:8989  fires up but NIS is not syncing, times out and crashes. Then start again, and it syncs for a while, time out and crashes again. Not very stable NIS.
#16

NCC's default port is 8989 -> that's why you have to connect to this port, if you want to use the web interface (the web interface talks to NCC).

NIS's default port is 7890 -> that's why you have to open this port in your router, if you want your NIS to be reachable to other nodes.

#17

NCC's default port is 8989 -> that's why you have to connect to this port, if you want to use the web interface (the web interface talks to NCC).

NIS's default port is 7890 -> that's why you have to open this port in your router, if you want your NIS to be reachable to other nodes.

Could this be why ncc is glitchy as hell when connecting to remote nis?
#18

@kodtycoon:
What do you mean? Can you explain more detailed?

#19

@kodtycoon:
What do you mean? Can you explain more detailed?


when i connect to local nis, everything runs fine.. when i connect to remote nis, ncc keeps disconnecting from remote nis(and i get the red bar along the top) then it will connect again but changing between accounts, or doing anything in the client is very slow to respond, if it does at all..
#20

Ok, then a closed port is not the reason for this behaviour.

It's more likely that the connection is bad (on both sides or at least one) or that the computer which is running NIS is too slow.

#21

Ok, then a closed port is not the reason for this behaviour.

It's more likely that the connection is bad (on both sides or at least one) or that the computer which is running NIS is too slow.


Mine is not even remote. It sits on the same computer and is getting that. Quite unstable actually. Is there some fork?
#22

Ok, then a closed port is not the reason for this behaviour.

It's more likely that the connection is bad (on both sides or at least one) or that the computer which is running NIS is too slow.


i was running an acer aspire with core i5 4gb ram and a higher model acer aspire with quadcore intel processor with 8gb ram both windows 8.1. one was with fiber power broadband speeds the other with shit internet and the problem was undistinguishable between either situation.

(i have to say, acer aspires are pretty damn good laptops)

i saw someone mention something about response time-outs being too fast/slow or something.. not sure.. il add an issue to github soon, havnt had time yet.
#23

Ok, if you run it local then this is an issue which should be solved before launch.

#24

Ok, if you run it local then this is an issue which should be solved before launch.


when i run nis locally its fine.. its when i connect to a remote nis that is the issue. i think BR could be aware of the issue but hasnt looked into the cause yet.
#25

You can run NIS local but connect to it remote… That is what I meant.

#26

You can run NIS local but connect to it remote.. That is what I meant.


ah ok :)
#27


@rockethead: what do you mean with "use localhost:7890"? Use in what way? To make requests in the browser?
Same question for the other port.


Yes, to make request in the browser.

http://localhost:7890 gives error
http://localhost:8989  fires up but NIS is not syncing, times out and crashes. Then start again, and it syncs for a while, time out and crashes again. Not very stable NIS.


Hi rockethead,

assuming that both NIS and NCC are started:

[url=http://localhost:7890]http://localhost:7890 gives an error of course, you are not supplying any api path like in [url=http://localhost:7890/chain/height]http://localhost:7890/chain/height.
[url=http://localhost:8989]http://localhost:8989 redirects to [url=http://127.0.0.1:8989/ncc/web/index.html]http://127.0.0.1:8989/ncc/web/index.html as wanted.

I don't know what you mean with "times out and crashes". Once NIS is booted it syncs and the version 0.4.48 is very stable, all my VPSes have been running many days with that version without any problem. Maybe you can supply the logs so I can get a better impression what is going wrong in your case.

Bloody Rookie
#28

Unable to start the client.

I have a VPS with a 32 bits firefox and a 32 bits chrome. I have a oracle 8 32 bits runtime environment. I try to start the client using http://bob.nem.ninja/webstart/ but in the middle java says it won't allow because a file specifying the security requirements is missing. I stop and shutdown the nem monitor icon on the taskbar and go to my computer settings, open the java icon and add to security exceptions http://bob.nem.ninja. Java says this is not advisable as this exception should only be applied to https. Anyway, i try again., this time the page starts but i have a red band on the top saying NIS status is unknown, after it keeps loading and the NCC starts. The icon at the task bar says "starting NIS" but immediately says again "NIS stopped". Now the red band on the web page says "NIS is not available".

I can see the nem intro page with that red band. On the right side i don't see any wallet (although i registered some NEM from NXT exchange). I try to create a new wallet thinking that maybe i can import my private key in the new wallet, but when creating the new wallet it displays a windows saying oops something the devs didn't think about. 500 error.

Now i can see there is wallet on the "open your wallet side" but when trying ti says the same "500 error".

If i download the jar for standalone and run it with java.exe -jar nem-core__V0.4.48-BETA.jar it says
no main manifest attribute, in nem-core__V0.4.48-BETA.jar


Please advice,

Thanks

EDIT ----------------

Solved, removed all java instalations with Javara and installed java again. Something was mixed up.

One little question. Is this client still on test network or should i be able to see my nems if i import the private key?

#29

This is still the test network.

#30

Thanks for replying.

Can i still enter the private key to see if it is working fine and i got my funds or is it dangerous?

Thanks

#31

It won't map to the same address as on the live network, so there is no point.


There is a way to test the validity of the address in the real address generation screen as I recall.

#32

I see. Thanks a lot for your replies!

#33

Is giving a error:generated block did not pass validation: FAILURE_ENTITY_UNUSABLE (org.nem.nis.n.tc a)

I'll have to put synchronize blockchain again?

Here is a log 21MB if they want to venture.
https://drive.bitcasa.com/send/o4KUuF4XKULChP34hJcZs1xvfCXzNv2Ty1jzhGcl2Kio

#34

@Icharles123: I think there is something wrong with your configuration. I see strange log entries like


07:48:05 WARNING No mapping found for HTTP request with URI [/] in DispatcherServlet with name 'Spring MVC Dispatcher Servlet' (org.springframework.web.servlet.PageNotFound noHandlerFound)
07:48:05 INFO Http Status Code 404: Not Found (org.nem.core.connect.ErrorResponse <init>)
07:48:06 WARNING No mapping found for HTTP request with URI [/favicon.ico] in DispatcherServlet with name 'Spring MVC Dispatcher Servlet' (org.springframework.web.servlet.PageNotFound noHandlerFound)


Also, your computer seems to have trouble to do time synchronization (that is the reason why you can't synchronize completely and probably the reason your block generation fails):


08:03:34 INFO Time synchronization: found 10 nodes to synchronize with. (org.nem.nis.time.synchronization.NisTimeSynchronizer ec)
08:03:35 WARNING Timer TIME SYNCHRONIZATION raised exception: org.nem.nis.time.synchronization.TimeSynchronizationException: No synchronization samples available to calculate network time.


Can you check if the nodes time is way off real time?

Bloody Rookie