Closed piyush-bansal1989 closed 6 months ago
Hi @piyush-bansal1989 ,
Thanks for bringing this to our attention. We have identified the issue. Will release in fix in the upcoming patch release scheduled.
@piyush-bansal1989 has been fixed with v1.0.2 release.
@vmsachin : Would you please help me understand what changes have been done?, I'm facing the same exception when connecting through transport error
@piyush-bansal1989 it was a naming change, we hadn't updated the service name in the make file for aerospike connection manager.
Are you able to build and run the Aerospike connection manager?
If you are seeing transport error, I'm guessing you are. Could you try and run the php file as root user ( sudo php ...
)
@piyush-bansal1989 it was a naming change, we hadn't updated the service name in the make file for aerospike connection manager. Are you able to build and run the Aerospike connection manager? If you are seeing transport error, I'm guessing you are. Could you try and run the php file as root user (
sudo php ...
)
@vmsachin : Yes I'm able to build and run the Aerospike connection manager. It's working when I run it through terminal with and without sudo. When I tried to run through apache (web server), it throws Exception transport error.
Hi Team
I'm reaching out to bring to your attention two issues I'm encountering with the Aerospike connection manager:
Socket File Access: After executing the make file within the aerospike-connection-manager directory, the socket file created through this is unable to access by the Apache user, transport error throws Missing asld.service: The make daemonize command executed under aerospike-connection-manager is not creating the asld.service file at given path. following is the output of the command