Today I tried to my USVN on http://192.168.1.2/usvn/ but unfotunately I get this shocking message !!!
Zend_Session::start() - /var/www/usvn/library/Zend/Session.php(Line:438): Error #2 session_start(): open(/var/lib/php5/sess_o58dtec91alc8r5q8821to20h0, O_RDWR) failed: Permission denied (13) Array /var/www/usvn/library/Zend/Session.php(Line:442): Error #2 session_write_close(): open(/var/lib/php5/sess_o58dtec91alc8r5q8821to20h0, O_RDWR) failed: Permission denied (13) Array /var/www/usvn/library/Zend/Session.php(Line:442): Error #2 session_write_close(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php5) Array
Trace:
/var/www/usvn/library/Zend/Session/Namespace.php:124 Zend_Session::start
/var/www/usvn/library/Zend/Auth/Storage/Session.php:87 Zend_Session_Namespace::__construct
/var/www/usvn/library/Zend/Auth.php:91 Zend_Auth_Storage_Session::__construct
/var/www/usvn/library/Zend/Auth.php:143 Zend_Auth::getStorage
/var/www/usvn/library/USVN/Controller.php:83 Zend_Auth::getIdentity
/var/www/usvn/library/Zend/Controller/Action.php:492 USVN_Controller::preDispatch
/var/www/usvn/library/Zend/Controller/Dispatcher/Standard.php:285 Zend_Controller_Action::dispatch
/var/www/usvn/library/Zend/Controller/Front.php:934 Zend_Controller_Dispatcher_Standard::dispatch
/var/www/usvn/public/index.php:5 Zend_Controller_Front::dispatch
So Can you please help!
Your apache/php installation is not able to write files in the session.save_path.
Make sure that the user under which apache runs has permissions to read and write in /var/lib/php5/.
Normally in every apache installation this should be true by default unless you messed up something with permissions.
After fixing that you're likely to encounter the same issue for usvn repository path. So keep that in mind. The php/apache user is NOT your shell user, so you should check for that user permissions, usually it's www-data or apache.
Related
I am setting up a spring boot application and when running it, it should generate a folder in the source directory (see step 3: https://www.baeldung.com/spring-boot-h2-database)
But when running the application I receive the following error:
org.h2.message.DbException: Log file error: "/data/sample.trace.db", cause: "org.h2.message.DbException: Error while creating file ""/data"" [90062-200]" [90034-200]
at org.h2.message.DbException.get(DbException.java:194)
at org.h2.message.TraceSystem.logWritingError(TraceSystem.java:294)
at org.h2.message.TraceSystem.openWriter(TraceSystem.java:315)
at org.h2.message.TraceSystem.writeFile(TraceSystem.java:263)
at org.h2.message.TraceSystem.write(TraceSystem.java:247)
at org.h2.message.Trace.error(Trace.java:194)
it seems to be a permission problem but I do not understand why. My current user, has admin permissons. What am I missing here?
When I encounter this problem on my machine I proceed through following steps:
If I don't know what user & group I am right now: $whoami && groups
What user is the program executed with (I'm not into Java so eg. PHP "echo exec('whoami');")
Who has access to the directory: $ls -la
3.1 If only owner has access and you are not the owner: $chown user:group file
3.2 If group and owner should have access consider: $chmod 770 file
Occasionally the first upload of artifacts during a GitLab pipeline fail.
I'm getting the following error message in the logs:
2019-08-01 13:43:14,149 [http-nio-8082-exec-187] [ERROR]
(o.j.s.b.p.t.FilePersistenceHelper:87) - Failed moving
'path_to_artifactory\filestore_pre\dbRecord123.bin' to
'path_to_artifactory\filestore\5e\5ecc5f719b4442b9b04f9010646d34917aca8ca2'.
Access to file denied null 2019-08-01 13:43:14,149
[http-nio-8082-exec-187] [ERROR] (o.a.w.s.RepoFilter :251) - Upload
request of products-stage-qa:file_to_upload failed due to {}
java.nio.file.AccessDeniedException: Failed to persist file with sha1:
5ecc5f719b4442b9b04f9010646d34917aca8ca2
This seems to happen only during builds, but not during other uploads directly by a user.
It doesn't happen all the time, and only on first tries. But I haven't found any logic when the first try fails or succeeds. It doesn't seem to have anything to do with file types or the like. I can't really determine if it has anything to do with network speeds though since I only have access to part of the infrastructure.
I found an open ticket with the same error message, but only for Conan and for us it only happens with ivy repositories
We are using Artifactory 6.9.1 and GitLab 12.0.3 starter
This looks to be a permission issue. You are getting an error message that states that the move failed due to "Access to file denied".
You can try to log in to the server using the "artifactory" user and manually move the file called "path_to_artifactory\filestore_pre\dbRecord123.bin" to "path_to_artifactory\filestore\5e\5ecc5f719b4442b9b04f9010646d34917aca8ca2" and see if you have any issues with this. To log in to the server with the "artifactory" user you can use the command "sudo -s -u artifactory".
You will also need to make sure that all filestore and its subdirectories are owned by the "artifactory" user and have the correct permissions.
Hope this helps.
Log rotate doesn't work very well.
So, when i execute command, I got a below error first time.
$ logrotate /etc/logrotate.d/systemname
error: error creating output file /var/lib/logrotate/logrotate.status.tmp: Permission denied
then i changed /var/lib/logrotate/ to 666
Error message change like below.
$ logrotate -f /etc/logrotate.d/systemname
error: error stat()ing state file /var/lib/logrotate/logrotate.status: Permission denied
Help me, how to solve this problem?
thanks.
I am assuming that you tried to run logrotate as unprivileged user ($ in the prompt), so you had no permissions for /var/lib/logrotate/.
I am trying to compile the alignment program AQUA with a .tcl script. I have compiled the programs and set the environmental variables in the .tcl file but I am still getting the following error;
tclsh AQUA.tcl mtDNA.fas
stderr couldn't execute "/home/shump/AQUA/muscle": permission denied
couldn't execute "/home/shump/AQUA/rascal": permission denied
couldn't execute "/home/shump/AQUA/normd": permission denied
One normd file does not exists yet (mtDNA.fas.muscle.normd), full stop
If anyone could put me in the right direction to solve this issue, I would appreciate it.
P
Most likely you need to set the execute bit permission on the files mentioned, using:
chmod +x /home/shump/AQUA/muscle /home/shump/AQUA/rascal /home/shump/AQUA/normd
Ok, so I'm trying to configure and install svnserve on my Ubuntu server. So far so good, up to the point where I try to configure sasl (to prevent plain-text passwords).
So; I installed svnserve and made it run as a daemon (also installed it as a startup script with the command svnserve -d -r /var/svn).
My repository is in /var/svn and has following configuration (to be found in /var/svn/myrepo/conf/svnserve.conf) (I left comments out):
[general]
anon-access = none
auth-access = write
realm = my_repo
[sasl]
use-sasl = true
min-encryption = 128
max-encryption = 256
Over to sasl, I created a svn.conf file in /usr/lib/sasl2/:
pwcheck_method: auxprop
auxprop_plugin: sasldb
sasldb_path: /etc/my_sasldb
mech_list: DIGEST-MD5
I created it in that folder as the article at this link suggested: http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sasl (and also because it existed and was listed as a result when I executed locate sasl).
Right after that I executed this command:
saslpasswd2 -c -f /etc/my_sasldb -u my_repo USERNAME
Which also asked me for a password twice, which I supplied. All going great.
When issuing the following command:
sasldblistusers2 -f /etc/my_sasldb
I get the - correct, as far as I can see - result:
USERNAME#my_repo: userPassword
Restarted svnserve, also restarted the whole server, and tried to connect.
This was the result from my TortoiseSVN client:
Authentication error from server: SASL(-13): user not found: unable to canonify
user and get auxprops
I have no clue at all in what I'm doing wrong. I've been scouring the web for the past few hours, but haven't found anything but that I might need to move the svn.conf file to another location - for example, the install location of subversion itself. which svn results in /usr/bin/svn, thus I moved the svn.conf to /usr/bin (although that doesn't feel right to me).
Still doesn't work, even after a new reboot.
I'm running out of ideas. Anyone else?
EDIT
I tried changing this (according to what some other forums on the internet told me to do): in the file /etc/default/saslauthd, I changed
START=no
MECHANISMS="pam"
to
START=yes
MECHANISMS="sasldb"
(Actually I had already changed START=no to START=yes before, but I forgot to mention it). But still no luck (I did reboot the whole server).
It looks like svnserve uses default values for SASL...
Check /etc/sasl2/svn.conf to be readable by the svnserver process owner.
If /etc/sasl2/svn.conf is owned by user root, group root and --rw------, svnserve uses the default values.
You will not be warned by any log file entry..
see section 4 of https://svn.apache.org/repos/asf/subversion/trunk/notes/sasl.txt:
This file must be named svn.conf, and must be readable by the svnserve process.
(it took me more than 3 days to understand both svnserve-sasl-ldap and this pitfall at the same time..)
I recommend to install the package cyrus-sasl2-doc and to read the section Cyrus SASL for System Administrators carefully.
I expect this is caused by the SASL API for the call
result = sasl_server_new(SVN_RA_SVN_SASL_NAME,
hostname, b->realm,
localaddrport, remoteaddrport,
NULL, SASL_SUCCESS_DATA,
&sasl_ctx);
if (result != SASL_OK)
{
svn_error_t *err = svn_error_create(SVN_ERR_RA_NOT_AUTHORIZED, NULL,
sasl_errstring(result, NULL, NULL));
SVN_ERR(write_failure(conn, pool, &err));
return svn_ra_svn__flush(conn, pool);
}
as you may see, handling the access failure by svnserve is not foreseen, only Ok or error is expected...
I looked in /var/log/messages and found
localhost svnserve: unable to open Berkeley db /etc/sasldb2: No such file or directory
When I created the sasldb to the above file and got the permissions right, it worked. Looks like it ignores or does not use the sasl database path.
There was another suggestion that rebooting solved the problem but that option was not available to me.