Skip to content
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

Support for database ports and sockets #5625

Closed
anonymous-matomo-user opened this issue May 1, 2008 · 2 comments
Closed

Support for database ports and sockets #5625

anonymous-matomo-user opened this issue May 1, 2008 · 2 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.

Comments

@anonymous-matomo-user
Copy link

There seems to be no functioning support for ports or sockets in terms of database connection.

As I found out with one of my sites you can append the port to the host-information like follows:

127.0.0.1;port=3307

Creating the tables now functions, but the port seems to be ignored as soon as you want to call the piwik-backend after installation, resulting in an error-message (couldn’t connect to database).
Therefore I played a little bit more and found that inserting “port=3307” in the config file fixes that problem too.
This time though it wouldn’t record any visits at all, and that’s where I’m stuck at the moment. Seems the database connectivity isn’t very continuous at the moment throughout the classes.

With another site I have a similar problem; I can’t tell piwik the right mysql-socket to use.
Keywords: database host port socket connection

@mattab
Copy link
Member

mattab commented May 6, 2008

It would be great if you had a more in depth look at it and provide a patch :)

@mattab
Copy link
Member

mattab commented Jun 11, 2008

(In 522) – fixes #5625 you can now install with a mysql port non 3306 by specifying your.host:4455

@anonymous-matomo-user anonymous-matomo-user added this to the Future releases milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Development

No branches or pull requests

2 participants