I’ve just migrated the Autocomplete-User plugin to work with the globale jQuery version (ui.autocomplete widget) used in the latest Trac versions.
Feel free to test it -> download
have fun
Mario
I’ve just migrated the Autocomplete-User plugin to work with the globale jQuery version (ui.autocomplete widget) used in the latest Trac versions.
Feel free to test it -> download
have fun
Mario
Suddenly the main RAID CIFS share stopped working. It seems for some reason nobody could mount this share anymore. All user got an access denied on mount attempts.
So what the hell was going on: The rather simple web interface wasn’t the burner, in fact the system log does not deserve the name Log 🙂
So mostly every RAID in this class is based on an embedded system driven by our friend Linux. This one is no exception.
So we first need the most important part,…. a working telnet or SSH connection. But a first “test” connection to the SS4400 device gave us “connection refused” as expected.
Luckily after some googling I found a hind that on this devices you can enable the SSH interface via a hidden CGI script.
http://hostname/ssh_controlF.cgi
Now you can login via “root” and your administration password.
By the way, this device comes with the Swiss Army Knife of Embedded Linux BUSYBOX which I also use for my embedded projects. I’m working with Busybox sense 2004 (version 0.94x), ….. great stuff :-).
But it seems, INTEL has some GPL violation with these devices. lol, ..On our bundled CDs we didn’t get any GPL sources from Busybox and Co? This is only mentioned in passing.
In our case a look into the system logs indicates that our RAID share had some file system problems. INTEL uses XFS as the file system on the storage device. Our system log was filled up with error messages of the file access layer.
In our case the solution was really simple. On device startup the file-system reports that there are errors, but then the corrupt partition is mounted and then ,… kabudl……
To fix this you first have to detach the corresponding RAID with “NASdetach”. Now you can unmount the partition and run the XFS repair binary “xfs_repair“.
After 10 – 15 min the repair should be finished.
Reboot the storage device and you should be able to access your share.
have fun
Mario
httpServer.cpp: In member function "std::string HttpJailServer::receive(int, e_t, size_t)": httpServer.cpp:145:36: error: "read"was not declared in this scope httpServer.cpp: In member function "void HttpJailServer::sendRaw(const char*,ze_t)": httpServer.cpp:216:49: error: "write" was not declared in this scope httpServer.cpp: In member function "void HttpJailServer::send(int, const stri, const string&)": httpServer.cpp:250:15: error: "close" was not declared in this scope
on building vpl_xmlrpc_jail-1.2 for Moodle VPL module, there seems to be a missing include for these methods.
Just add,
#include <unistd.h>
to the httpServer.cpp, these should fix it.
have fun
Mario
For some reasons I got the meaningful error message :
Parser Error Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. Parser Error Message: Could not load type 'WebService.Global'. Source Error: Line 1: <%@ Application Codebehind="Global.asax.cs" Inherits="WebService.Global" Language="C#" %> Source File: /global.asax Line: 1
In my case I solved the problem in changing the build output path from bin\x68\Debug to : bin
hope this helps anyone
have fun
Mario
Download overview.php from here and replace it with your existing.
have fun Mario
There are couple of bug request in the moodle bug tracking system, but for 2.1+ there is unfortunately no commit in master which fixes this issue.
So if you do not want to wait for an official release take a look at -> link. Follow the walkthrough how to update Yui an this should fix the IE9 problems.
have fun
SELECT ue.userid, ue.status, ue.timestart, ue.timeend FROM {user_enrolments} ue JOIN {enrol} e ON e.id = ue.enrolid WHERE ue.userid $usql AND e.status = :estatus AND e.courseid = :courseid GROUP BY ue.userid, ue.status, ue.timestart,ue.timeend
and @row 851
SELECT ue.userid, ue.status, ue.timestart, ue.timeend FROM {user_enrolments} ue JOIN {enrol} e ON e.id = ue.enrolid WHERE ue.userid = :uid AND e.status = :estatus AND e.courseid = :courseid GROUP BY ue.userid,ue.status, ue.timestart, ue.timeend
have fun
After upgrading from debian squeeze I run into the problem that every commit was failing with “Couldn’t perform atomic initialization“.
See Debian bug report
My apache logs are showing :
[error] [client ] Couldn’t perform atomic initialization [500, #200029]
[error] [client ] Couldn’t perform atomic initialization [500, #200029]
[error] [client ] SQLite compiled for 3.7.4, but running with 3.7.3 [500, #200030]
So it looks like that libapache2-svn is build against libsqlite3 3.7.4 which is currently in Sid. In Squezze we have libsqlite3 3.7.3
A quick fix would be to take the libsqlite3 package from Sid for now.
have fun